You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I do not remember if there is any specific reason: I assume whoever added it (could have been me :) ) copied setting from non-key handling.
PR looks good, will add some notes.
cowtowncoder
changed the title
Question and PR about ZonedDateTimeKeyDeserializer
Limited formats accepted by ZonedDateTimeKeyDeserializerMar 23, 2024
cowtowncoder
changed the title
Limited formats accepted by ZonedDateTimeKeyDeserializer
Only DateTimeFormatter.ISO_OFFSET_DATE_TIME accepted by ZonedDateTimeKeyDeserializerMar 23, 2024
Hello.
Is there any reason for specifying DateTimeFormatter.ISO_OFFSET_DATE_TIME as the format for parsing ZonedDateTimes in ZonedDateTimeKeyDeserializer?
This prevents valid ZonedDateTime keys from being deserialised.
If the second parameter to .parse isn't specified, then all formats supported by .parse are allowed.
I have raised a PR to change this: #305
The text was updated successfully, but these errors were encountered: