KamoCRM

Server timestamps read as UTC and shown in the member's zone; switches named; landing-card test sees the console hubs

Fixkamo-internal
Shipped
November 14, 2026 at 6:11 PM UTC
Author
Kamo
Commit
d0bd75c

check-server-timestamps (50 hits -> 0): every flagged parse of an offset-less service timestamp now goes through parseServerDate / serverEpochMillis / toServerDate, and every browser-zone render (toLocale*String, bare Intl.DateTimeFormat, next-intl format.dateTime, which has no timeZone configured) now goes through useFormatters() or formatInZone with the member's zone. Notable: the vault date helpers take the member zone; the market inventory From/To filter compares member-zone calendar days instead of mixing UTC-midnight and browser-local bounds; siAuth secondsLeft (same misparse, unflagged only because the file has no `new Date(`) uses serverEpochMillis. No allowlist entries or opt-outs added. check-switch-aria (2 -> 0): LicenseManagerDialog and the vault Share With Kamo switch name themselves through slotProps.input, which MUI 7 actually forwards. settingsLandingCards.i18n test: the Platform Console hub cards use dotted ids (console.overview, ...), which the literal-id pattern skipped, so the count check failed and those eight cards' copy was never verified. The pattern now admits dotted ids; all 92 cards resolve. SiAuthRequestHost test mocks useFormatters, which the dialog now uses for its stamps.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing