[#151] Add option to deserialize both null and missing as None #184
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.
Add optional argument
deserializeNullAsNone: boolto option.WithSkippableOptionFields(SkippableOptionFields).Compare with the current, and now default
falsebehavior:Fixes #151, #176, #182.
Note: I have changed my mind since this comment, in that this setting only affect
optionandvoption, but notSkippable. The reason is thatSkippableexists precisely for fields that must be skipped, and so thatSkippable<T option>can be used to explicitly distinguish between missing and null. This ability should be usable alongsideoptionvalues that can be deserialized from either null or missing.