Separate ISO and default serializers #393
Closed
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,
X.Formats.ISOandX.parse()/X.toString()behave subtly differently; currently, it's the case forLocalDateTimeandLocalTime.With this change, every entity that supports custom formats obtains a separate default serializer in addition to the
ISO 8601 serializer, which now properly delegates to the corresponding
DateTimeFormat.Fixes #351