You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The spec in http://doc.apsstandard.org/2.1/spec/rql/ mandate dates to be in ISO UTC format. This also is the date format on the JSON spec and the format returned by JS Date.toJSON. This means the DateUtil class should not fail on strings like 2016-07-17T02:59:59.999Z.
The thing, though is how that it converts to a LocalDateTime. I'm not sure if dropping the time zone info (the Z in the string) is always the correct solution since some masochists developers might use something different than UTC for their timezone.
The text was updated successfully, but these errors were encountered:
Thanks for reminding me of this one, I have already think about providing extensions or allowing client code to specify the formatting conversion of dates at a global or per mapping basis. Will include this feature in the next milestone.
First of all, great job!
The spec in http://doc.apsstandard.org/2.1/spec/rql/ mandate dates to be in ISO UTC format. This also is the date format on the JSON spec and the format returned by JS
Date.toJSON
. This means theDateUtil
class should not fail on strings like2016-07-17T02:59:59.999Z
.The thing, though is how that it converts to a LocalDateTime. I'm not sure if dropping the time zone info (the Z in the string) is always the correct solution since some masochists developers might use something different than UTC for their timezone.
The text was updated successfully, but these errors were encountered: