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
With the change introduced by #211 any parser that uses commands can no longer use flags.PassAfterNonOption. I believe this is a bug, and I'll be working on a fix—please let me know if it's intended behaviour so I can leave it be (and instead change our code).
This change restores the old behaviour of PassAfterNonOption working
together with commands so that a command would (also) get everything
after the first non-option, while also preserving the new behaviour of
those non-options landing in the positional array if provided.
The behaviour for when a command and a positional array are both
present continues to be weird (but it's unclear whether there's a
non-weird way out of that one other than failing with a "don't do
that").
chipaca
added a commit
to chipaca/go-flags
that referenced
this issue
Sep 27, 2018
This change restores the old behaviour of PassAfterNonOption working
together with commands so that a command would (also) get everything
after the first non-option, while also preserving the new behaviour of
those non-options landing in the positional array if provided.
The behaviour for when a command and a positional array are both
present continues to be weird (but it's unclear whether there's a
non-weird way out of that one other than failing with a "don't do
that").
With the change introduced by #211 any parser that uses commands can no longer use
flags.PassAfterNonOption
. I believe this is a bug, and I'll be working on a fix—please let me know if it's intended behaviour so I can leave it be (and instead change our code).As an example, this:
produces
The text was updated successfully, but these errors were encountered: