-
Notifications
You must be signed in to change notification settings - Fork 155
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
Remove time calendars #1188
Remove time calendars #1188
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1188 +/- ##
==========================================
+ Coverage 93.55% 95.72% +2.17%
==========================================
Files 19 19
Lines 7961 9175 +1214
Branches 1264 1384 +120
==========================================
+ Hits 7448 8783 +1335
+ Misses 506 386 -120
+ Partials 7 6 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
7c2b51d
to
b703589
Compare
b703589
to
c5c507f
Compare
c5c507f
to
9fc3bf1
Compare
- Remove Calendar.timeFromFields(), Calendar.timeAdd(), Calendar.timeUntil(), Calendar.hour(), ..., Calendar.nanosecond(). - Remove PlainTime.withCalendar(). - Remove now.plainTime(). - Remove the calendar argument from PlainTime constructor. - Remove the calendarName option from PlainTime.toString(). - Throw if there's a non-ISO calendar passed to PlainTime.from(). - The value of PlainTime.calendar is always the ISO calendar. - Leave the names of the slots, the properties returned from PlainTime.getFields() and PlainTime.getISOFields(). See: #522
It was decided in #260 that overflow: 'constrain' should not affect invalid values coming from ISO strings, but it seems that it crept back in during a refactor. Fix this and add a test so that it doesn't regress again.
9fc3bf1
to
e3e40b6
Compare
I have addressed the comments, so landing this now; if there are further comments please let me know and I'll follow up. |
Closes: #522