docs: update changelog

runner-prompt
TorchedSammy 2022-05-30 21:10:45 -04:00
parent 7dc438cc97
commit 02fb7c3238
Signed by: sammyette
GPG Key ID: 904FC49417B44DCD
1 changed files with 11 additions and 4 deletions

View File

@ -54,10 +54,17 @@ having and using multiple runners.
This is probably one of (if not the) biggest things in this release. This is probably one of (if not the) biggest things in this release.
- **Breaking Change:** MacOS config paths now match Linux. - **Breaking Change:** MacOS config paths now match Linux.
- Overrides on the `hilbish` table are no longer permitted. - Overrides on the `hilbish` table are no longer permitted.
- **Breaking Change:** Runner functions are now required to return 3 values: - **Breaking Change:** Runner functions are now required to return a table.
user input, exit code, and error. User input has been added to the return to It can (at the moment) have 4 variables:
account for runners wanting to prompt for continued input, and to add it - `input` (user input)
properly to history. - `exitCode` (exit code)
- `error` (error message)
- `continue` (whether to prompt for more input)
User input has been added to the return to account for runners wanting to
prompt for continued input, and to add it properly to history. `continue`
got added so that it would be easier for runners to get continued input
without having to actually handle it at all.
- **Breaking Change:** Job objects and timers are now Lua userdata instead - **Breaking Change:** Job objects and timers are now Lua userdata instead
of a table, so their functions require you to call them with a colon instead of a table, so their functions require you to call them with a colon instead
of a dot. (ie. `job.stop()` -> `job:stop()`) of a dot. (ie. `job.stop()` -> `job:stop()`)