Adds support for NodaTime types in Hot Chocolate.
Just call AddNodaTime
on your schema builder like so:
SchemaBuilder.New()
// ...
.AddNodaTime()
.Create();
Format: One Zone ID from these
Literal example: "Europe/Rome"
References:
Literal example: "-123:07:53:10.019"
References:
Literal example: "2020-02-20T17:42:59Z"
References:
Literal example: 7
References:
Literal example: "2020-12-25"
References:
Literal example: "2020-12-25T13:46:78"
References:
Literal examples:
"12:42:13"
"12:42:13.03101"
References:
Literal examples:
"2020-12-25T13:46:78+02"
"2020-12-25T13:46:78+02:35"
References:
Literal examples:
"2020-12-25+02"
"2020-12-25+02:35"
References:
Literal examples:
"13:46:78+02"
"13:46:78+02:35"
References:
Literal examples:
"+02"
"+02:35"
References:
Literal examples:
"P-3W3D"
"PT139t"
"P-3W3DT139t"
References:
There's nothing close to a standard for timezoned date-times. Therefore this library chooses to follow the order of the ZonedDateTime
constructor and define a format with a LocalDateTime
pattern followed by a timezone ID followed by an offset.
Feel free to override this behavior.
Literal examples:
"2020-12-31T18:30:13 UTC +00"
"2020-12-31T19:40:13 Europe/Rome +01"
"2020-12-31T19:40:13 Asia/Kathmandu +05:45"
References: