Correct operator precedence in find conditionals #213
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
Thanks! Can you do a rebase? (3.6-rc was deleted) |
Previously the `type` option was only being applied to the first `-name` option, rather than both. Fixes #212.
Member
|
Took the liberty of rebasing it for you. 👍 (Merging now without CI, because I didn't change any of the files and it was green before. 👍) |
Contributor
Author
|
Many thanks (got sidetracked hehe) :-) |
tao12345666333
pushed a commit
to tao12345666333/python
that referenced
this pull request
Jun 28, 2018
Correct operator precedence in find conditionals
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously the
typeoption was only being applied to the first-nameoption, rather than both.Fixes #212.