entoas: handle nillable fields #423
Merged
Conversation
This file contains 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
masseelch
force-pushed
the
entoas/nilable
branch
from
cf5c36a to
92a6cf7
Compare
giautm
pushed a commit
that referenced
this pull request
Feb 15, 2023
* entoas: handle nillable fields * go mod tidy * go generate
giautm
pushed a commit
that referenced
this pull request
Feb 15, 2023
* entoas: handle nillable fields * go mod tidy * go generate
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Thid PR adds support for
Optional()andNillable()fields. There are three cases to handle:Optional()This field has to be non-required in a POST request body and the model itself.
Nillable()This field has to be required in a request body, but the result (model) might contain a (database) NULL value.
Optional()andNillable()Same as 1.