This repository has been archived by the owner on Nov 7, 2019. It is now read-only.
Allow custom DateTimeFormatters #34
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
…ializer/Deserializer.
|
Sounds good to me. One thing I do need before merging it in is CLA from: https://github.com/FasterXML/jackson/blob/master/contributor-agreement.pdf Thank you for the contribution, looking forward to merging it! |
…TimeSerializer/Deserializer.
…Serializer/Deserializer.
…Serializer/Deserializer.
…lizer/Deserializer.
cowtowncoder
added a commit
that referenced
this pull request
Jul 27, 2015
Allow custom DateTimeFormatters
|
Thank you for the contribution! Will be in 2.6.1. |
cowtowncoder
added a commit
that referenced
this pull request
Jul 27, 2015
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.
Allow users of the api pass in a custom formatter to the LocalDateSerializer/Deserializer.
This is a possible approach to solving issue #17
We only implemented what was necessary in LocalDateSerializer and LocalDateDeserialize, which were the two classes we needed to solve our problem. If this approach looks good we are willing to extend this to the other relevant Serializers and Deserializers.