This repository has been archived by the owner on May 20, 2021. It is now read-only.
Allowing explicitly putting null #52
Open
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
GRiMe2D
commented
Jan 18, 2018
| /** | ||
| * The style that wrap should ignore nil values or explicitly put JSON null value | ||
| */ | ||
| var wrapNilStyle: WrapNilStyle { get } |
There was a problem hiding this comment.
However, using bool value provides easier integration but using enum makes possible to add more options in future
|
That would be useful for me too, any idea if this will be merged or any workaround for that? I need to send |
|
@hebertialmeida In Cartfile just replace Wrap to I'll tag it later |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Sometimes we need JSON null values, especially when API requests with PATCH method where null values mean "delete" the property