Add nullable field types #1
Open
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.
Current State
@ksherman doesn't like that he can't unset a field by explicitly setting it to
nullthrough APIs that define parameters withdefparams. This happens because the library strips allnull-value fields, regardless of how they'renull.With this PR
This PR introduces nullable field types (e.g.
:string_nullable) that allow you to explicitly set a value tonulland see thatnullvalue after validating params. Fields that are not explicitly set will continue to be ignored.Example