-
Notifications
You must be signed in to change notification settings - Fork 30
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
Default Date encoder doesn't preserve milliseconds #43
Comments
Can't recall why, but some questions:
|
The standard ISO 8601 (https://en.wikipedia.org/wiki/ISO_8601) doesn't define a precise format, hence the trouble. According to DZone Jackson default behaviour is to serialize dates as millisecond from epoch. Interesting,
I have no idea what JS default behaviour is. |
Hi,
I've noticed that the default encoder for dates doesn't preserve the milliseconds precision
Is this a deliberate decision? wouldn't be better for the default encoder to preserve data as much as possible rather than truncating it?
The text was updated successfully, but these errors were encountered: