-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid subcommand doesn't show any errors #259
Comments
@mikedotexe related PR #51 Note that just re-enabling strict mode is problematic, as then loading config fails when command doesn't support all of the options in config. It should be possible to solve by loading and merging config with options manually vs going through yargs. Best place to put it is likely yargs middleware: |
Super helpful context, thank you. I took another approach here Edit: you replied 2 minutes before this in PR. looking into this more |
# Conflicts: # bin/near-cli.js # index.js
Finally got this through, thanks for the patience, Illia. |
Currently running non-existent / invalid sub-command doesn't result in any error.
The text was updated successfully, but these errors were encountered: