-
Notifications
You must be signed in to change notification settings - Fork 163
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
Normative: Reject too large dates in ToTemporalMonthDay #3054
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3054 +/- ##
=======================================
Coverage 96.14% 96.14%
=======================================
Files 21 21
Lines 9928 9929 +1
Branches 1801 1801
=======================================
+ Hits 9545 9546 +1
Misses 336 336
Partials 47 47 ☔ View full report in Codecov by Sentry. |
Thanks. We'll discuss this in the next champions meeting. |
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.
Could we make the diff to be presented as minimal as possible? Ideally just the two edits in plainmonthday.html. Since the PlainYearMonth change is unobservable, I'd be happy to accept a PR for it beforehand.
…earMonth The call to `CalendarYearMonthFromFields` will already reject too large dates, but adding an explicit step makes it more obvious that `ISODateToFields` doesn't require support for mapping large ISO dates to calendar dates. And it also aligns `ToTemporalYearMonth` with `ToTemporalMonthDay` after #3054.
…earMonth The call to `CalendarYearMonthFromFields` will already reject too large dates, but adding an explicit step makes it more obvious that `ISODateToFields` doesn't require support for mapping large ISO dates to calendar dates. And it also aligns `ToTemporalYearMonth` with `ToTemporalMonthDay` after #3054.
…y strings This adds coverage for the normative change in tc39/proposal-temporal#3054, which specifies that implementations must throw on out-of-range dates in RFC 9557 strings for non-ISO calendars.
Tests are in tc39/test262#4389. |
3ce9a20
to
19f17f6
Compare
Draft until approved in TC39. |
Approved in the TC39 plenary of 2025-02-18. I'll pull in the test262 update before merging this. |
…y strings This adds coverage for the normative change in tc39/proposal-temporal#3054, which specifies that implementations must throw on out-of-range dates in RFC 9557 strings for non-ISO calendars.
…y strings This adds coverage for the normative change in tc39/proposal-temporal#3054, which specifies that implementations must throw on out-of-range dates in RFC 9557 strings for non-ISO calendars.
19f17f6
to
a143609
Compare
Implements the normative change from the previous commit in the reference code.
a143609
to
1cfbd3d
Compare
Follow-up to #3008 / #3002 to reject too large dates.