In the error handler at https://github.com/terminalwire/ruby/blob/main/gem/terminalwire-rails/lib/terminalwire/rails.rb#L174, when a CLI user tries a command that doesn't exist or other invocation error, the command always does exit 0, instead of a non-zero exit code indicating an error.
Also, the error message is written to stdout instead of stderr, but this is less of a concern.
Also, tangentially related, there doesn't seem to be any way for the user to set context.exit. That handler is always going to set it to 1 or 0.
In the error handler at https://github.com/terminalwire/ruby/blob/main/gem/terminalwire-rails/lib/terminalwire/rails.rb#L174, when a CLI user tries a command that doesn't exist or other invocation error, the command always does
exit 0, instead of a non-zero exit code indicating an error.Also, the error message is written to stdout instead of stderr, but this is less of a concern.
Also, tangentially related, there doesn't seem to be any way for the user to set
context.exit. That handler is always going to set it to1or0.