Skip to content

Ensure millisecond component in the serialized string when returning DateTime #58

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

Closed
mursilsayed opened this issue Apr 19, 2022 · 2 comments

Comments

@mursilsayed
Copy link

DateTime implements RFC 3339 which defines time-secfrac optional as: time-secfrac = "." 1*DIGIT (Meaning 1 or more DIGIT). This allows for an unlimited numbers of digits for the fractional part of the second.

Update DateTime to ensure that millisecond component of the serialized string is not optional and it always consist of exact three digits representing milliseconds.
DateTime serialization with format yyyy-MM-dd'T'HH:mm:ss.SSSZ (set '000' in milliseconds position when milliseconds are not set).

See Non optional exact milliseconds

@IndyNaessens
Copy link

@mursilsayed can be closed I suppose

@dondonz
Copy link
Member

dondonz commented Nov 9, 2022

Fixed by #59

@dondonz dondonz closed this as completed Nov 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants