8a9cffd076
UTC timestamps rendered with date-fns format() or toLocaleTimeString() use the runtime's local timezone, causing the server (UTC) and client (PDT) to produce different output. suppressHydrationWarning was hiding the mismatch but the visual time-flip was still visible on load. - Add useHasMounted hook (useSyncExternalStore-based, no extra render cycle) - Gate UTC timestamp formatting behind isMounted in EventSchedule and UpcomingCalendarPanel; SSR always renders the stable YYYY-MM-DD eventDate string - Fix formatEventDate in date-utils.ts (and EventSchedule private copy) to parse YYYY-MM-DD as local midnight instead of UTC midnight, fixing the off-by-one day bug for UTC-negative users across all callers Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
59 lines
2.4 KiB
TypeScript
59 lines
2.4 KiB
TypeScript
/**
|
|
* Converts a datetime-local input value (local time, no timezone info)
|
|
* to a UTC ISO string for server submission.
|
|
*
|
|
* `datetime-local` inputs use the format "YYYY-MM-DDTHH:MM" and do NOT accept
|
|
* ISO strings with a timezone designator (e.g. "2026-03-11T17:00:00.000Z").
|
|
* Setting an ISO UTC string directly on a datetime-local input causes the browser
|
|
* to silently clear the field value. Use this function with a separate hidden input
|
|
* to hold the converted UTC value before form submission.
|
|
*
|
|
* Returns null when value is empty, nullish, or not a valid date.
|
|
*
|
|
* NOTE: The returned ISO string (e.g. "2026-03-11T17:00:00.000Z") is intentionally
|
|
* incompatible with datetime-local inputs, which only accept "YYYY-MM-DDTHH:MM".
|
|
* Setting a Z-suffixed string on a datetime-local input causes browsers to silently
|
|
* clear the field. Always write the result to a separate hidden input, not back to
|
|
* the datetime-local input itself.
|
|
*/
|
|
import { format } from "date-fns";
|
|
|
|
/**
|
|
* Format a YYYY-MM-DD date string for display (e.g. "Apr 9").
|
|
* Returns null when the value is missing or unparseable — callers decide how to handle that case.
|
|
*/
|
|
export function formatEventDate(dateStr: string | null | undefined): string | null {
|
|
if (!dateStr) return null;
|
|
try {
|
|
const [year, month, day] = dateStr.split("-").map(Number);
|
|
return format(new Date(year, month - 1, day), "MMM d");
|
|
} catch {
|
|
return null;
|
|
}
|
|
}
|
|
|
|
/**
|
|
* Produces a stable sort key for upcoming calendar events.
|
|
*
|
|
* Bracket events carry a full ISO game timestamp in `earliestGameTime`; all-compete
|
|
* events (auto racing, golf) use the ISO timestamp in `earliestGameTime` when a start
|
|
* time has been set, or fall back to the date-only `eventDate` string. Events with
|
|
* neither sort to the far future so they appear last.
|
|
*
|
|
* The mixed comparison of ISO timestamps and "YYYY-MM-DD" strings works correctly via
|
|
* lexicographic order because both share the same date prefix; a date-only string always
|
|
* sorts before a same-day timestamp (shorter string < longer string with "T" suffix).
|
|
*/
|
|
export function toEventSortKey(e: {
|
|
eventDate: string | null;
|
|
earliestGameTime: string | null;
|
|
}): string {
|
|
return e.earliestGameTime ?? e.eventDate ?? "9999-12-31";
|
|
}
|
|
|
|
export function localDateTimeToUtcIso(value: string | null | undefined): string | null {
|
|
if (!value) return null;
|
|
const date = new Date(value);
|
|
if (isNaN(date.getTime())) return null;
|
|
return date.toISOString();
|
|
}
|