-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Annotate braintree's MultipleValueNodeBuilder.in_list method #16235
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
d266512
Annotate braintree's MultipleValueNodeBuilder.in_list method
cuu508 339dbe8
Add overload for the case where the first argument is a list
cuu508 048f170
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] c051a51
Fix in_list to expect a single argument if the 1st argument is a list
cuu508 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since a list can be used as such a sequence of values for the first argument, I think it might be worth adding an overload for this case.
(Please, import
Unusedfrom_typeshed)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@donbarbos oops, missed that. Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not familiar with braintree, but I assume calling
in_listif a list as first argument and further arguments would indicate a bug or misunderstanding of the API. In this case I think it's safer to remove the*valuesargument from the first overload.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, if the first argument is a list, it uses it and ignores the rest:
Passing a list and anything following it would not throw an error, but also would not make any sense. I removed the
*values: Unusedbit from the PR.