fix: consider timestamp format for JSON protocol serialization #3182
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.
Issue #, if available:
The JSON protocol (Rest-JSON, JSON 1.1) serialization ignores the timestampFormat trait of timestamp shapes in c2j model which causes it to default to unixTimetsamp format instead of the prescribed format.
Description of changes:
These changes add support for timestampFormat trait for JSON protocols. It also abstracts out the handling of timestamp shape serialization for different serialization protocols as they tend to share similar implementations.
Added tests around these changes for various protocols.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.