Skip to content

fix(react): preserve manual date validity and Korean display - #96

Merged
jlc488 merged 4 commits into
mainfrom
fix/date-picker-validity-ko
Oct 15, 2026
Merged

jlc488 merged 4 commits into
mainfrom
fix/date-picker-validity-ko

Conversation

@jlc488

@jlc488 jlc488 commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

Manual invalid or incomplete date input could be repaired on blur/Enter, and queued Ark synchronization frames could overwrite a newer draft. Give the DDS native text input one controlled owner while reusing the finished Ark calendar, trigger and portal. Preserve invalid/partial text and native validity; expose canonical ISO dates through onChange and an optional onValidityChange callback whose value is null when invalid. Korean display uses YYYY/MM/DD; storage/API remains YYYY-MM-DD.

Calendar selection returns focus to the input with a cancellable lifecycle frame. Existing label/error associations, readOnly/disabled behavior, date-only bounds and controlled reset/echo behavior are preserved.

Validation: 51 related React DOM assertions, corrected Seoul/UTC/Los_Angeles cases, React typecheck/build, and fresh packed consumers on React 19.3.0 and 18.3.1 passed. The packed gate verifies public DatePicker types, browser-free Node/worker SSR, strict control/outside DOM identity with expected Ark portal promotion/disposal, and valid/invalid native jsdom input. Existing CI runs unchanged.

Includes a patch Changeset under the existing fixed release group. Consumer Save handlers must guard validity.valid and validity.value; production Admin/Contract HTTP protection remains consumer integration work.

@jlc488
jlc488 merged commit a0031b0 into main Oct 15, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant