fix: guard toISOString calls against Invalid Date in Firefox
The previous fix guarded startAt/endAt numeric values but left startDate/endDate calling .toISOString() on the potentially invalid result of localToUtc(), which throws TypeError in Firefox when zonedTimeToUtc returns Invalid Date. Now falls back to raw date .toISOString() when the UTC conversion is invalid.
This commit is contained in:
1 parent
2cd9657ae1
commit
816b51096d
1 file changed
+10
-6
@@ -7,14 +7,18 @@ export function useDateParameters() {
|
||||
} = useDateRange();
|
||||
const { timezone, localToUtc, canonicalizeTimezone } = useTimezone();
|
||||
|
||||
const startAtValue = +localToUtc(startDate);
|
||||
const endAtValue = +localToUtc(endDate);
|
||||
const utcStart = localToUtc(startDate);
|
||||
const utcEnd = localToUtc(endDate);
|
||||
const startAtValue = +utcStart;
|
||||
const endAtValue = +utcEnd;
|
||||
const isStartValid = Number.isFinite(startAtValue);
|
||||
const isEndValid = Number.isFinite(endAtValue);
|
||||
|
||||
return {
|
||||
startAt: Number.isFinite(startAtValue) ? startAtValue : +startDate,
|
||||
endAt: Number.isFinite(endAtValue) ? endAtValue : +endDate,
|
||||
startDate: localToUtc(startDate).toISOString(),
|
||||
endDate: localToUtc(endDate).toISOString(),
|
||||
startAt: isStartValid ? startAtValue : +startDate,
|
||||
endAt: isEndValid ? endAtValue : +endDate,
|
||||
startDate: isStartValid ? utcStart.toISOString() : startDate.toISOString(),
|
||||
endDate: isEndValid ? utcEnd.toISOString() : endDate.toISOString(),
|
||||
unit,
|
||||
timezone: canonicalizeTimezone(timezone),
|
||||
};
|
||||
|
||||
Reference in new issue
Block a user