-
Notifications
You must be signed in to change notification settings - Fork 152
new: Add support for explicit nullable arguments #421
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
new: Add support for explicit nullable arguments #421
Conversation
jriddle-linode
left a comment
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.
Changes look good, will require a couple small changes to spec parser PR but nothing major. Good to merge before parser IMO.
|
Any update on this? @lgarber-akamai |
|
@zliang-akamai I plan on updating and re-requesting reviews on this once the OpenAPI spec has been merged to main 👍 |
febca0b to
ba557fa
Compare
zliang-akamai
left a comment
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.
Everything looks good!
zliang-akamai
left a comment
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.
The refactoring was awesome!
📝 Description
This change allows users to specify
nullas a value for fields that are marked asnullablein the API spec. This is useful for situations where the API may have certain functionality tied to having a certain value be explicitlynull(e.g. RDNS resets)e.g.
NOTE: This will need to be partially reworked after the spec parser refactor, but the change should be relatively straightforward.
Resolves #266
✔️ How to Test