You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently print the help text on every command failure. Printing usage information is great when an error occurs parsing CLI options. However, it's noisy and unhelpful for errors reported afterwards.
Let's silence the help text after we have parsed CLI options. For example, in the run subcommand:
We currently print the help text on every command failure. Printing usage information is great when an error occurs parsing CLI options. However, it's noisy and unhelpful for errors reported afterwards.
Let's silence the help text after we have parsed CLI options. For example, in the
run
subcommand:lilypad/cmd/lilypad/run.go
Lines 33 to 37 in b467d0f
we could set
cmd.SilenceUsage
totrue
after handling anyProcessJobCreatorOptions
errors.The silenced error output can be tested by temporarily returning an error from the first line of the
runJob
function:lilypad/cmd/lilypad/run.go
Lines 46 to 47 in b467d0f
The text was updated successfully, but these errors were encountered: