feat(form): native date, time and date-time fields

[kozmaadrian]

TODO

• Release the da-sc-sdk with date/time format validation PR and re-vendor the published version — this PR currently vendors a dev build of the SDK in nx/deps/da-sc-sdk/dist/. The SDK source changes (format extraction, value-shape validation, docs) live on a separate da-sc-sdk branch.

---

Summary

Adds native date, time, and date-time field support to the SC form editor, driven entirely by the JSON Schema format keyword. A single form-date component wraps the browser's native <input> (date / time / datetime-local), so authors get real pickers and keyboard entry — including on mobile — instead of a plain text box.

Test URL: https://da.live/form?nx=formdate#/exp-workspace/frescopa/forms/date-input-test

Before: the time, date, and date-time inputs are simply text inputs.

After: the time, date, and date-time fields use native HTML input elements.

format: date (floating date)

format: date-time (the UI displays the users local time, however saves the same time in UTC always)

format: time (float time, no timezone)

How it works

The editor maps the schema format to one parameterized component:

schema format	native input	stored value
date	date	YYYY-MM-DD (floating, no timezone)
time	time	HH:MM (floating, no timezone)
date-time	datetime-local	YYYY-MM-DDTHH:MM:00Z (absolute instant, UTC)

• date / time are floating — they mean the same everywhere (a publish date, store opening hours).
• date-time is store-UTC / display-local — the picker shows and edits the value in the viewer's local zone and converts back to UTC on save, so the instant stays stable no matter which zone an author edits from.

Validation

Validation is owned by the SDK (the trust boundary — a script writing directly can't bypass it), not the widget:

• date / time are checked for real calendar/clock validity (2026-02-30, 24:00 are rejected).
• date-time is deliberately stricter than RFC 3339: only UTC Z with zero seconds is accepted, so the editor and any SDK-only writer produce one identical, comparable value (offsets, non-zero seconds, and sub-minute precision are rejected).
• Empty optional fields are treated as absent — format is not enforced on an empty value.

Edge cases

• Pre-1900 dates carry sub-minute Local Mean Time offsets; the local→UTC conversion rounds to the minute so those can't leak seconds and break the canonical form.
• Early-CE years are zero-padded to 4 digits; the native year field is capped to 4 digits (some browsers otherwise allow 6).

Compatibility

• Additive for any schema that doesn't use these formats — nothing changes.
• Schemas that already declare format: date | time | date-time now render as pickers and get validated. Existing documents whose values aren't canonical (especially date-times with an offset or non-zero seconds) would surface a validation error, so it's worth a quick audit of existing date-time data. Validation is not gated on save, so this surfaces an error rather than blocking.

Testing

• Unit tests for the widget, the local↔UTC helpers, and the editor dispatch, verified across time zones (incl. Europe/Zurich and America/New_York, which exercise the LMT edge). Full suite green.

[aem-code-sync]

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch.
In case there are problems, just click the checkbox below to rerun the respective action.

• Re-sync branch

Commits

• 07a2de9 ✅ (latest)
• 45e6b8e ✅
• 91d1099 ✅
• fca596d ✅
• 4a72bf5 ✅