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
Well... Although formally correct, this substantially reduces the usability of such parsing. The likelihood of "30" and such being an intentional representation of "30th century" is virtually zero. It would help a lot, if this behavior were an opt in.
Behavior
This should error/return invalid date instead of parsing.
Similar code in golang returns an error when parsing '30'.
https://go.dev/play/p/L8_zo40vNNA
The text was updated successfully, but these errors were encountered: