Uh oh!
There was an error while loading. Please reload this page.
GH-230 removing unwanted/unneeded/unused cloudevent serializer and deserializer and hence dependency - #231
Conversation
…serializer and hence dependency
| .addModule(new SimpleModule() | ||
| .addSerializer(ZonedDateTime.class, new ZonedDateTimeSerializer()) | ||
| .addDeserializer(ZonedDateTime.class, new ZonedDateTimeDeserializer())) |
There was a problem hiding this comment.
How do we make sure that it won't fail in serialization/deserialization? Does Jackson support these date formats OOTB?
There was a problem hiding this comment.
what matters here is the objectmapper pulled from here is properly serializating/deserializing dates/times when used with the models stuffed in our sdk, right ?
and I believe it's the case :
the only 2 dates found in our json model are actually currently exposed as String in the Registration class : they were no need for this in the first place ...
There was a problem hiding this comment.
AFAIK the only place where we used Date type in our jackson powered model are in the aem module when serializing aem event
Related Issue
GH-230
Motivation and Context
removing unwanted/unneeded/unused cloudevent serializer and deserializer and hence dependency
It was introduced here Add support for Registration V2 API #126
@JsonFormatwe still have this
events_ingress: replace ourCloudEventmodel by the Open sourcecloudevents/sdk-javamodel . #16 pendingbut for now I propose we remove this annoying dependency
Types of changes
Checklist: