Skip to content

fix: address positional argument strict() bug introduced in #766#784

Merged
bcoe merged 2 commits into7.xfrom
766-fix
Feb 18, 2017
Merged

fix: address positional argument strict() bug introduced in #766#784
bcoe merged 2 commits into7.xfrom
766-fix

Conversation

@bcoe
Copy link
Member

@bcoe bcoe commented Feb 18, 2017

this addresses a bug related to positional command arguments in strict mode:

command <foo> [bar]

@nexdrew does this solve the issues that you brought up in slack?

@bcoe bcoe requested a review from nexdrew February 18, 2017 07:37
@bcoe
Copy link
Member Author

bcoe commented Feb 18, 2017

@nexdrew checked in one more update; noticed while testing the regression introduced in #766 that we were executing command handlers when validation failed, this was an order of operation bug.

@bcoe bcoe merged commit 57a8490 into 7.x Feb 18, 2017
@bcoe bcoe deleted the 766-fix branch February 18, 2017 20:08
@bcoe
Copy link
Member Author

bcoe commented Feb 18, 2017

@nexdrew I'm going ahead and landing these couple tweaks, so that I can start adding some tests to your default command branch.

If we find more issues around commands and the global/local changes, we can land further patches.

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.

1 participant