-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
Support for milliseconds #13
Labels
enhancement
New feature or request
Comments
I looked to this and need some help from OG devs inside this repo, so let's look into this. Firstly, I see that [email protected] Also I see that when we |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I'd like to request the possibility to explicitly work with milliseconds during the various operations this library offers. The uppercase S is a common template token for parsing and formatting milliseconds, with the ability to vary the number of decimal places using multiple S (e.g.
.S
,.SS
,.SSS
).Parsing a datetime with milliseconds already works when not using a custom format, for example
parse("2022-08-03 16:56:54.477")
returns the appropriate date object2022-08-03T14:56:54.477Z
.Another thing I encountered is that
tzDate
seems to remove the milliseconds part of the date, bothtzDate("2022-08-03 16:56:54.477", "Europe/Berlin")
andtzDate(parse("2022-08-03 16:56:54.477"), "Europe/Berlin")
return2022-08-03T14:56:54.000Z
.The text was updated successfully, but these errors were encountered: