New issue
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
relnote(121): Date.parse
fixes and additions
#30234
relnote(121): Date.parse
fixes and additions
#30234
Conversation
Preview URLs External URLs (6)URL:
(comment last updated: 2023-11-18 08:44:29) |
Does this also have corresponding docs updates required? See #30235 (comment) |
Even though there are quite a few associated bugs, I think it'd be helpful to link each element in your list to the relevant Bugzilla ticket. WDYT about adding that context to your list? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added relevant Bugzilla links - thanks!
Co-authored-by: Zach Fox <3409031+zfox23@users.noreply.github.com>
Entry
Date.parse()
now accepts several additional date formats:Year > 9999 for
YYYY-MMM-DD
format (e.g.19999-Jan-01
)MMM-DD-YYYY
(e.g.Jan-01-1970
)Milliseconds for non-ISO date formats (e.g.
Jan 1 1970 10:00:00.050
)Day of week at the beginning of formats which were being rejected, such as:
Wed, 1970-01-01
Wed, 1970-Jan-01
The day of week does not need to be correct, or a day of week at all; for example,
foo 1970-01-01
works.Other
Date.parse()
fixes:YYYY-M-DD
andYYYY-MM-D
are no longer assumed GMT as an ISO dateYYYY-MM-DD
would beBugzilla
In the order of the entries: