Editorial: Clarify CalendarResolveFields TypeError vs. RangeError circumstances #2994
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…cumstances RangeError is thrown only when non-unset fields can provide sufficient data, which implies that a TypeError was not thrown. Fixes tc39#2993
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2994 +/- ##
=======================================
Coverage 96.42% 96.42%
=======================================
Files 21 21
Lines 10641 10641
Branches 1819 1819
=======================================
Hits 10261 10261
Misses 322 322
Partials 58 58 ☔ View full report in Codecov by Sentry. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
RangeError is thrown only when non-unset fields can provide sufficient data, which implies that a TypeError was not thrown.
Fixes #2993