Output behavior for failing commands

[plamber]

Hi,
the CLI outputs the error message and immediately after the command help. I understand that the main idea behind is to immediately provide some help or guidance to somebody not working often with the CLI.

On the other hand, this behavior is a little bit annoying when you are writing and testing scripts and your output is throwing an exception of any type. I would rather prefer to call explicitly the --help parameter whenever I need help.
It would follow also the handling of other command line tools. They do not immediately output the whole documentation just because a command is returning an exception.

My suggestion is to remove this automated behavior for command exceptions and ask users to use the --help parameter if they need help.

What are your thoughts?

Thank you for your feedback,
Patrick

[waldekmastykarz]

Initially, we have been showing just the error. Just recently, we switched the behavior to automatically show help, thinking that if something went wrong, you'll likely need help to figure out what's wrong. I'd love to hear more if our thinking was correct or if we should stick to showing just the error, like @plamber mentioned.

@pkskelly @alexandair what do you think?

[waldekmastykarz]

Based on the feedback solicited on twitter, we decided to keep the output as-is for now and allow users to configure it, when we add support for configuration.