We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The T separator is just convention. It can be any single character.
T
https://github.com/Urigo/graphql-scalars/blob/master/src/scalars/iso-date/formatter.ts#L21
Parsing milliseconds with this regex is not allowing comma , separator, only dot .
,
.
https://github.com/Urigo/graphql-scalars/blob/master/src/scalars/iso-date/formatter.ts#L49
It also doesn't appear to handle 2-digit timezones. ie +00 instead of +0000
+00
+0000
Postgres default timestamptz formatter returns strings like 2024-04-01 01:00:00,000+00
timestamptz
2024-04-01 01:00:00,000+00
So this library will fail to parse that in at least 3 different ways, even though it's perfectly valid ISO-8601 format.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The
Tseparator is just convention. It can be any single character.https://github.com/Urigo/graphql-scalars/blob/master/src/scalars/iso-date/formatter.ts#L21
Parsing milliseconds with this regex is not allowing comma
,separator, only dot.https://github.com/Urigo/graphql-scalars/blob/master/src/scalars/iso-date/formatter.ts#L49
It also doesn't appear to handle 2-digit timezones. ie
+00instead of+0000Postgres default
timestamptzformatter returns strings like2024-04-01 01:00:00,000+00So this library will fail to parse that in at least 3 different ways, even though it's perfectly valid ISO-8601 format.
The text was updated successfully, but these errors were encountered: