fix(console): Create User marks a missing email on its input, in the user's language - #28649

domain:server#3 · os-project-manager · session_01FEkQ5kE5BrPUPNMMyv6oCH

Requested by Leehom · project thread

Fixes #28289

Clause-②: yes (widening) — @object-ui/core newly exports refusalFieldErrors (reached through the package entry's export * from './actionResponse.js'); no server answer, accept set or spec key changes.
Metadata-protocol: none

维护者速读

• 改了什么：Console 的「创建用户」对话框里，邮箱留空提交后，服务端返回的 required 字段错误现在直接标在「邮箱」输入框下（手机号登录开启时也标「手机号」），用用户当前语言的「X 为必填项」，不再只在按钮上方显示一句英文。
• 为什么改：Create User refusal for a missing email answers the generic INVALID_REQUEST, so the console cannot localise it per field #28289 的服务端那一半（PR fix(plugin-auth): Create User with no email answers the field-level VALIDATION_FAILED refusal #28354）已经按字段返回 error.fields，但 Console 读字段错误的那个函数只认 error.details.fields，没读到 error.fields，对话框也从不根据服务端结果标字段，所以非英文用户看到的还是英文。契约评审 6539927716 定了 A：由 Console 用自己的翻译措辞。
• 风险与回滚：低。只在拒绝结果带有 required 字段条目、且该字段正是对话框里画出的参数时才标字段；其它拒绝照旧显示服务端原文。回滚即 revert 本 PR。
• 先看：ui/packages/app-shell/src/views/ActionParamDialog.tsx（refusalParamMarks 与 handleSubmit 里的失败分支）；ui/packages/core/src/actions/actionResponse.ts（refusalFieldErrors 多读一处 error.fields）；ui/packages/app-shell/src/utils/flowResponse.ts（apiActionRefusalResult）。
• 两分钟验证：pnpm --dir ui exec vitest run packages/app-shell/src/hooks/__tests__/useConsoleActionRuntime.createUserRequiredField-28289.test.tsx，预期 6/6 通过（main 上 4 个失败）。
• 需要你做的：无，席位落地。

What changes

• @object-ui/core, actions/actionResponse.ts: refusalFieldErrors, the reader behind ActionResult.fieldErrors, now reads a refusal's error.fields as well as error.details.fields and the legacy inner fields. Both envelope members are on the spec's EnhancedApiErrorSchema (fields, and details whose documented example carries details.fields). The data and action doors put a thrown validation failure under details.fields; plugin-auth's Create User builds its own refusal and names the list fields, and the action door relays it whole. The function is now exported, so the api handlers use the same reader the /actions refusals go through (no second spelling).
• @object-ui/app-shell, utils/flowResponse.ts: new apiActionRefusalResult(res, json, fallback, locale): the failed ActionResult for a non-2xx type: 'api' answer, with error from apiActionFailureMessage (unchanged) and fieldErrors from refusalFieldErrors when the refusal named any. Both api hosts use it: useConsoleActionRuntime (list and page actions, both the action door and the direct fetch) and RecordDetailView (its door branch and its direct fetch).
• @object-ui/app-shell, views/ActionParamDialog.tsx: on a refused run, refusalParamMarks turns each required entry whose field names a collected param into the dialog's own mark, actionDialog.requiredError with the param's localized label (the same key and rendering the dialog's client-side required check uses, so it reads "邮箱 为必填项" in Chinese). When every entry is marked, the refusal box is not drawn, because it would only repeat the marks in English. An entry the dialog cannot mark (another code, a param it does not draw, an unresolved or carry-over param) keeps the box with the server's text. A refusal with no entries keeps today's display. Typing in a marked input clears its mark, as before. The header's objectui#13161 paragraph no longer says the dialog marks no field.
• .changeset/28289-create-user-required-field-mark.md: @object-ui/core patch, @object-ui/app-shell patch. Core's files[] ships dist; app-shell is private, and its code ships in the Console bundle, as the other app-shell changesets record.

Not touched, as ruled: the server answer, any error code, packages/spec.

Tests

PROBE28289 400 {"success":false,"error":{"code":"VALIDATION_FAILED","message":"Email is required","httpStatus":400,"fields":[{"field":"email","code":"required","message":"Email is required"}]}}
Test Files  1 passed (1) · Tests 1 passed | 58 skipped (59) · VERDICT command-exit 0

Acceptance notes

• The runner still toasts a refused run's error (the server's English sentence) as it did before; the dialog no longer repeats it when every entry is marked. Whether the toast should step aside for a fully marked refusal is the runner's call, not changed here.
• With phone sign-in on, the server sends one required entry for each of Email and Phone Number, so both inputs read "required" although either one satisfies the server. That is the marking the order asked for; a wording of "one of these" would need a second key.
• The platform carries a refusal's field list in two envelope members (error.details.fields from the data and action doors, error.fields from plugin-auth's own refusals). This PR reads both; it does not choose one.

Verification

• Every reading above and below is at head cd271105.
• Derived gate list: node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack on this diff gave 34 commands. Each ran with its exit code captured before any pipe: all 34 exit 0. --ran reconciliation: 34 derived, 34 run, 0 NOT-MEASURED, 0 UNRUN. check:type-check-debt first answered exit 3 (PREREQUISITE NOT MET: its closure build queued behind this branch's own test run on the shared lock); re-run under the lock it answered OK, 0 raw tsc errors, exit 0.
• pnpm check:new-line-citations (from ui/): 0 new citations.
• origin/main moved 13 commits past the base a798ae8f; none touches a file this diff changes, so the branch was not merged with it.

Generated by Claude Code