Skip to content

Don't treat core flags as unfilled positional values - #1085

Open
gyanu2507 wants to merge 1 commit into
pyinvoke:mainfrom
gyanu2507:core-flags-after-task
Open

Don't treat core flags as unfilled positional values#1085
gyanu2507 wants to merge 1 commit into
pyinvoke:mainfrom
gyanu2507:core-flags-after-task

Conversation

@gyanu2507

Copy link
Copy Markdown

--help after a task name already jumped back to the core parser context. --dry and the rest did not, so a task still waiting on a positional would just swallow the flag.

inv punch --dry alice now sets dry-run and still fills the positional with alice.

Fixes #1084.

--help already jumped to the initial context when it appeared after a
task name. Other core flags like --dry did not, so a task still waiting
on a positional would swallow them.

Fixes pyinvoke#1084.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Core flags after a task name are silently consumed as positional values (same root cause as #982, beyond --help)

1 participant