fix(console): after a language switch, date cells format in the new language, not the stale server locale - #27624

domain:ui#2 · os-bill · session_01Utp6CY2n1JmZZKrHgtp9jC

Requested by Bill · project thread
Fixes #27498
Clause-②: no
Metadata-protocol: none

维护者速读

• 改了什么:头像菜单切换语言后,console 的本地化提供者在「本人 sys_user 行被写入」时重新读取 /auth/me/localization;日期格式化器仍只有一个(formatDate 经 useDisplayLocale),未新增第二个。
• 为什么改:切换语言会先换界面语言、触发 console 重挂载,再写 sys_user.locale;重挂载发出的读取可能先于写入到达服务器,拿回旧的 en-US 并整个会话保留,于是中文界面下表格日期显示 Oct 11,整页加载才变 2026年10月11日。
• 风险与回滚:只动 console 一个文件,写入本人 sys_user 行时多一次 GET;回滚即 revert 本 PR。
• 先看:ui/apps/console/src/LocalizationFetchProvider.tsx(新的 useDataInvalidation 依赖与 signal 一行);LocalizationFetchProvider.test.tsx 新的 describe 块。
• 两分钟验证:pnpm --dir ui exec vitest run apps/console/src/LocalizationFetchProvider.test.tsx,预期 18 个测试全绿,其中 4 个新用例名以 re-reads after a write 开头。
• 需要你做的:无,席位落地。

What changes

LocalizationFetchProvider (console) now reads GET /api/v1/auth/me/localization again whenever the signed-in user's own sys_user row is written through the data-invalidation bus, and that re-read opts out of joining a request still in flight from before the write.

Cause, measured on a running stack. The endpoint's locale is the caller's language: their own sys_user.locale when set, else the request's Accept-Language, else the deployment default. useDisplayLocale ranks it above the active UI language, and every grid / record date renderer formats with it. The avatar-menu switch (useLanguageSelection) changes the UI language first and writes sys_user.locale second. The UI-language change remounts the metadata subtree (key={language} in ConnectedShellInner), which remounts this provider, and the remount's read can reach the server before the column write commits. It then answers the previous language (for a user with no stored language yet, the browser's Accept-Language, en-US), and nothing ever read again. Result: Chinese headers, chips and footer (all t-driven) beside Oct 11 / Nov 1 / Nov 18 dates, until a full page load re-read the now-written column.

Why the record page differed. It is not a second formatter and not grid-specific. The record page reads the same useDisplayLocale; the walkthrough's record page was a fresh page load, whose boot read sees the committed column. Reached in the same session by clicking the row, the record page also read Oct 11, 2026 before this change (measured below).

Fix at the cause. The provider subscribes with useDataInvalidation('sys_user', userId) (the same bus useSignedInUserLocale already reads; every adapter write reaches it through useMutationInvalidationBridge). The language switch's own write therefore triggers a read that starts after the write has settled. Because sharedGetJson shares a promise with any overlapping GET of the same URL, a re-read passes an AbortController signal, which opts it out of sharing (and aborts it if superseded or unmounted); the boot read keeps sharing with seedTenantLanguage() (objectui#5544). The existing cancelled guard drops a stale answer that settles late; the catch now returns first when cancelled so an abort is not treated as a transient failure. The profile page's language card writes the same row and is covered by the same subscription.

The ruling "Format grid date cells through the same locale-aware formatter the record page uses. No second date formatter." holds: no formatter, renderer or useDisplayLocale line changed.

Tests

New describe block in ui/apps/console/src/LocalizationFetchProvider.test.tsx, probing useDisplayLocale() plus formatDate('2026-10-11', undefined, { locale, alwaysShowYear: true }), the face a grid cell paints:

• a read that lost the race with the language write is replaced after the write: boot read answers en-US (Oct 11, 2026), a sys_user write for the signed-in user re-reads, the probe shows zh-CN|2026年10月11日.
• the re-read does not join a request still in flight from before the write: the boot read is held pending; the write's re-read issues its own request and lands zh-CN; the held request settling late with en-US is dropped.
• a write to another user's row reads nothing again and signed out, a sys_user write reads nothing again.

The block resets the shared in-flight registry after each case, so a pending request from a failing case cannot be joined by the next one.

Acceptance notes

• Same symptom, second door, not fixed here (reported to the seat): a signed-in user with no stored sys_user.locale whose UI language comes from the device (for example 中文 picked on the sign-in page) gets Nov 18 dates under Chinese headers on every load, deterministically: the endpoint answers the Accept-Language rung (en-US), and useDisplayLocale ranks it above the UI language. Measured on this stack with the column reset to null and objectui-locale = zh. Closing it means changing useDisplayLocale's documented precedence or having the endpoint say which rung answered, a design call outside this card.
• The useDisplayLocale docblock says the tenant locale is "Frequently undefined"; on this stack an authenticated read always answered a locale (en-US from the header or deployment rung). Not edited here.
• The object description staying English under zh-CN (A unit of work inside a project.) is the showcase bundle's coverage, out of scope per the card.

Verification

Generated by Claude Code