-
-
Notifications
You must be signed in to change notification settings - Fork 7.4k
[R] add null checks to nullable api parameters #21629
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
7 commits
Select commit
Hold shift + click to select a range
a4aac2a
[R] check optional parametrs for null before evaluating param conditions
mattpollock 1d7111f
update petstore
mattpollock 4c7a454
handle isNullable when checking api parameters
mattpollock 3cec95d
update samples
mattpollock d1cd514
allow not-nullable parameters to be missing
mattpollock 1392b09
update samples
mattpollock ac0c717
samples
mattpollock 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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
thanks for the pr
2 questions:
looks like required parameters are processed again for null check. shall we update the block in line 195 instead?
since this is in the
allParamsloop/list, that means optional parameters (if defined) will be processed as well. would optional parameters work in this new code block (null check)?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.
This update was in response to @Mattias-Sehlstedt above
I was matching "required" to the R
missing()check and "nullable" the Ris.null()check. I added the!missing({{paramName}})to the null checks to avoid an error in the event that an a parameter that is "not required" but "is not nullable" and is set toNULL. I cannot think of any cases where an optional parameter should not be nullable though.To your questions:
missingin the line 195 block. If I add a null check there then optional and nullable will by handled the same way in R clients. I'm fine with this if you prefer it.missing()and then checked foris.null()if the parameter is not nullable.I think this is ready to go, but what I actually care about is the fix in a4aac2a. If we need further discussion on the nullable checks I'm happy to move those commits to a fresh PR.