Replies: 4 comments 7 replies
-
Sure, good idea. Do we need this to be configurable? Or just change the behavior for everybody? |
Beta Was this translation helpful? Give feedback.
-
I think I can implement it. I am also leaning towards default with no preferences settings. Barring unforeseen complications, you can expect it in a few days. |
Beta Was this translation helpful? Give feedback.
-
This is tracked in #244 |
Beta Was this translation helpful? Give feedback.
-
Version 0.8.3 is released with this update. Thanks for the suggestion. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I typically see command line utilities throw a "unknown command" error and exit when a user tries to call a command that doesnt exist. Currently bashly will just show the usage command instead. Is there any plans to allow an error to be thrown instead or is there a way to accomplish this with Bashly's current features?
So for example
my-cli unknown-cmd
would display an error:Unknown command: "unknown-cmd"
and then exit.Beta Was this translation helpful? Give feedback.
All reactions