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
I cannot find any good explanation other than an error for this behaviour. It seems trying to get a localized string for a PlainMonthYear throws RangeError: Mismatching Calendars.
The bundled code is minified and likely extremely optimized, so it is hard to say exactly what happens. The problem happens in toEpochMillis, where resolvedOptions is
If I convert to a PlainDate first and only format the month/year (Temporal.PlainYearMonth.from('2024-11').toPlainDate({ day: 1 }).toLocaleString('en', { month: 'long', year: 'numeric' })), it works just fine. It appears that PlainYearMonth has strictCalendarChecks enabled in its ClassFormatConfig, so I'm guessing part of this is intentional, but it does not seem like there should be an error here.
I don't know if this is somehow related to my environment, but I don't understand what I could have done to affect any of this.
The text was updated successfully, but these errors were encountered:
I cannot find any good explanation other than an error for this behaviour. It seems trying to get a localized string for a
PlainMonthYear
throwsRangeError: Mismatching Calendars
.The bundled code is minified and likely extremely optimized, so it is hard to say exactly what happens. The problem happens in
toEpochMillis
, whereresolvedOptions
isand the
slotsList
isIf I convert to a
PlainDate
first and only format the month/year (Temporal.PlainYearMonth.from('2024-11').toPlainDate({ day: 1 }).toLocaleString('en', { month: 'long', year: 'numeric' })
), it works just fine. It appears thatPlainYearMonth
hasstrictCalendarChecks
enabled in itsClassFormatConfig
, so I'm guessing part of this is intentional, but it does not seem like there should be an error here.I don't know if this is somehow related to my environment, but I don't understand what I could have done to affect any of this.
The text was updated successfully, but these errors were encountered: