-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ZonedDateTime
serialization with @JsonFormat.pattern
never uses it while WRITE_DATES_WITH_ZONE_ID
enabled
#333
Comments
may be related to #330 |
#330 was about Wrt issue here, I think class-level |
ZonedDateTime
serialization with @JsonFormat.pattern
never uses it while WRITE_DATES_WITH_ZONE_ID
enabled
@cowtowncoder Is this closed? 👀 |
@JooHyukKim I did close it, yes. Is there remaining work? |
Yeah I thought #334 would be related |
Yes, closed due to #334 fixing this issue. Feel free to re-open issues if they are wrongly closed (with a note). |
Yeah, was asking because the mentioned PR #334 is still open 👀 |
Whops. So I did not actually yet merge it. My bad, thank you for reminder @JooHyukKim :) |
…ture.WRITE_DATES_WITH_ZONE_ID` (#334)
Now merged. |
Search before asking
Describe the bug
Hi, I'm using JavaTimeModule() in my app with SerializationFeature.WRITE_DATES_WITH_ZONE_ID enabled and there's a strange thing:
When JsonFormat-annotation with pattern is added:
Current object is always serialized as an ISO_ZONED_DATE_TIME, e.g. "2024-11-15T18:27:06.921054+01:00[Europe/Germany]", the pattern is not taken into account.
Could you give a hint if this is expected behaviour, thank you!
Version Information
2.18.1
Expected behavior
{"time":"2024-12-02 16:30:00 CET"}
The text was updated successfully, but these errors were encountered: