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 object 2022-08-03T14:56:54.477Z.
Another thing I encountered is that tzDate seems to remove the milliseconds part of the date, both tzDate("2022-08-03 16:56:54.477", "Europe/Berlin") and tzDate(parse("2022-08-03 16:56:54.477"), "Europe/Berlin") return 2022-08-03T14:56:54.000Z.
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
tzDateseems 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.