Skip to content

Change default of SerializationFeature.WRITE_DATES_AS_TIMESTAMPS to false in 3.0 #4845

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.

Sign up for GitHub

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

Jump to bottom
Closed
cowtowncoder opened this issue Dec 10, 2024 · 2 comments
Closed

Change default of SerializationFeature.WRITE_DATES_AS_TIMESTAMPS to false in 3.0 #4845

cowtowncoder opened this issue Dec 10, 2024 · 2 comments
Labels
3.0-release-notes Issues relevant for 3.0 release notes. 3.0 Issue planned for initial 3.0 release

Comments

@cowtowncoder
Copy link
Member

cowtowncoder commented Dec 10, 2024 •
edited
Loading

(note: part of proposed changes via https://github.com/FasterXML/jackson-future-ideas/wiki/JSTEP-2)

It seems that the default of writing basic Date/Time values as numeric timestamps is something that should be changed: while this is more efficient than the alternative of writing Date/Time value as Strings, most users expect Strings, and most frameworks seem to change the default.

So the proposal is to change the default accordingly.
@cowtowncoder cowtowncoder added the 3.0 Issue planned for initial 3.0 release label Dec 10, 2024
@cowtowncoder
Copy link
Member Author

Change has been approved: we can proceed with change!

@JooHyukKim JooHyukKim mentioned this issue Feb 1, 2025
Merged
JooHyukKim added a commit to JooHyukKim/jackson-databind that referenced this issue Feb 1, 2025
@JooHyukKim
Fix tests post FasterXML#4845
288d8bd
cowtowncoder pushed a commit that referenced this issue Feb 5, 2025
@JooHyukKim
[Jackson3.0] Fix #4845: change `SerializationFeature.WRITE_DATES_AS_T…
961c128 
…IMESTAMPS` to `false` in 3.0 (#4946)
@cowtowncoder cowtowncoder mentioned this issue Feb 5, 2025
Closed
@cowtowncoder
Copy link
Member Author

Defaults have been changed for 3.0.0-rc1.

@pjfanning pjfanning added the 3.0-release-notes Issues relevant for 3.0 release notes. label Apr 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
3.0-release-notes Issues relevant for 3.0 release notes. 3.0 Issue planned for initial 3.0 release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cowtowncoder @pjfanning