fix(fields,components): a date typed in a form that the picker cannot read is a field error that refuses submit - #27623

domain:ui#2 · os-bill · session_01Utp6CY2n1JmZZKrHgtp9jC

Requested by Bill · project thread
Fixes #27483
Clause-②: yes (widening)
Metadata-protocol: none

维护者速读

• 改了什么：记录表单里手输一个读不懂的日期（如 13/45/2026）时，该字段当场标红并显示提示，点「创建」被拒、对话框不关、不发请求；改对或清空后才能保存。
• 为什么改：原来日期控件不写入读不懂的文本，表单值保持为空（编辑时保持旧值），照常保存并弹成功提示，用户以为日期已存好。
• 风险与回滚：只新增一个可选的控件回调和一条表单校验项，只对 date / datetime 控件生效；回滚即还原本 PR，无数据迁移。
• 先看：ui/packages/components/src/renderers/form/form.tsx（新校验项 invalidInput 与回调）、ui/packages/fields/src/widgets/date-picker/DatePickerField.tsx（上报与撤回）、ui/packages/fields/src/widgets/types.ts（新属性的契约说明）。
• 两分钟验证：pnpm --dir ui exec vitest run packages/fields/src/__tests__/date-picker-invalid-text-blocks-submit-27483.test.tsx，预期 5 条全绿。
• 需要你做的：无，席位落地。

What changes

The date / datetime picker never writes text that names no date. In a record form that meant the form value stayed what it was (empty on create, the old date on edit), the submit went through and the success toast fired. Per the triage ruling, the unparseable text is now marked invalid through the form's existing field validation, the way a missing required value is.

• onInvalidInputChange (@object-ui/fields, FieldWidgetComponentProps): a new optional widget prop. A widget that parses typed text fires it with the message to show when the committed text names no value, and with null once the text is valid, cleared, or the widget unmounts. Its doc comment names its producer (the date picker's two faces) and its consumer (the form renderer). It is added to toHostProps' HOST_PLUMBING_KEYS, so the compile-time partition still holds and FieldEditWidget delivers it when a host passes it.
• DatePickerField / DateTimePickerField: report on change only (not on every render), withdraw on unmount, and report nothing while readonly. A widget given the callback leaves the message text to the form's FormMessage, as the error slot already does; a host that passes none (the grid's inline editor, the action-param and bulk-action dialogs) keeps the picker's own notice, byte for byte. aria-invalid is set either way.
• form renderer (@object-ui/components): a per-field invalidInputMessages map (a ref, beside requiredMessages, read by the validator at call time) and a first rules.validate entry, invalidInput, that refuses while a message is held. The callback stores the message and runs trigger(name), so the error shows when the user leaves the field, not only at submit; a withdrawal clears only an invalidInput error. stripRegisteredFieldProps forwards the callback to the date / datetime widgets only, so no other widget spreads an unknown handler onto its DOM.
• The time widget is a native input[type=time] and shares neither the parser nor the commit path, so it is untouched.

Tests

• ui/packages/fields/src/__tests__/date-picker-invalid-text-blocks-submit-27483.test.tsx (new, real form renderer plus the production registration of the picker): typing 13/45/2026 and leaving the field shows the form message and aria-invalid, with no second notice; pressing Create is refused (the form scrolls to the field) and onSubmit is never called; correcting the text clears the error and saves 2026-10-20; clearing it lets an optional empty date save; a valid typed date saves (control); datetime refuses the same way.
• ui/packages/components/src/renderers/form/__tests__/form-invalid-input-refuses-submit-27483.test.tsx (new, probe widget): a report becomes the field message at once and refuses submit; a withdrawal clears it and the submit goes through; only field:date receives the callback, field:lookup does not.
• DatePickerField-12622.test.tsx (updated, the existing "not written, and says so" pin is kept as is): with a host callback the picker reports the message (containing the text and the format), draws no own notice, reports null after a valid commit, on clear and on unmount; datetime reports too.

Acceptance notes

• Hosts outside the record form (FieldEditWidget for the grid and record-page inline edit, ActionParamDialog, BulkActionDialog) pass no callback today, so there the picker still shows its own notice and does not block the host's save. Not reproduced here and not filed; noted as the remaining surface of the same channel.
• The message shown is the picker's existing fields.datePicker.invalid string ("Not saved: ... is not a date. Type it as FORMAT, or pick one from the calendar."), so no i18n key was added.
• The merge of main met the record-currency change in stripRegisteredFieldProps; both allow-list lines are kept.

Verification

Head 81611c8a. Test readings at bc5108de (after the one merge of main); c4826848 only types the two new test files' probe and registrations instead of casting to any (both packages' type-check exit 0 and the four pin files 33/33 there), and 81611c8a only changes the changeset's declaration to Clause-②: yes (widening): FieldWidgetComponentProps is exported from @object-ui/fields, and the new key is optional, so no consumer breaks. The derived gates are re-run at 81611c8a.

Generated by Claude Code