Fix: Print help instead of throwing error on unknown commands#1157
Conversation
This ensures `clasp x` shows the help menu instead of failing with a stack trace. Co-authored-by: sqrrrl <346343+sqrrrl@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
This ensures `clasp <unknown command>` properly outputs an error message and shows the help menu instead of crashing with a raw unhandled stack trace. Added a unit test. Co-authored-by: sqrrrl <346343+sqrrrl@users.noreply.github.com>
This ensures `clasp <unknown command>` properly outputs an error message and shows the help menu instead of crashing with a raw unhandled stack trace. Added a unit test. Co-authored-by: sqrrrl <346343+sqrrrl@users.noreply.github.com>
Resolves #1156 by ensuring
clasp <unknown_cmd>properly prints the command help and exits with status1, instead of printing a raw unhandled stack trace. Added a unit test.PR created automatically by Jules for task 17979674611158503235 started by @sqrrrl