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
I noticed that when a command-line "option" is required, but not given in the task invocation, the reported names use underscores instead of hyphens.
This isn't a huge deal, but it does present a bit of an impediment to a user responding to what is wrong. If I saw that error message without existing knowledge of invoke, I would think that I need to add e.g. --param_1 asdf to my command-line. A straightforward workaround would be to assign a default value, test for it, and raise an appropriate error from the body of the task.
It would also be helpful to have the - or -- prefix in this case, but I imagine this is a harder problem to solve since not all ways to enter the task are necessarily from the command-line? Anyway, I couldn't find an existing report for this, so I figured I'd file one.
I noticed that when a command-line "option" is required, but not given in the task invocation, the reported names use underscores instead of hyphens.
This isn't a huge deal, but it does present a bit of an impediment to a user responding to what is wrong. If I saw that error message without existing knowledge of
invoke
, I would think that I need to add e.g.--param_1 asdf
to my command-line. A straightforward workaround would be to assign a default value, test for it, and raise an appropriate error from the body of the task.It would also be helpful to have the
-
or--
prefix in this case, but I imagine this is a harder problem to solve since not all ways to enter the task are necessarily from the command-line? Anyway, I couldn't find an existing report for this, so I figured I'd file one.Reproduction
click for `invoke --debug dummy` output
The text was updated successfully, but these errors were encountered: