Skip to content

Version Packages#361

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

Version Packages#361
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@tailor-platform/app-shell@1.8.0

Minor Changes

  • a4f735c: Add DateField, DatePicker, and Calendar components (@internationalized/date + Base UI implementation)

    Introduces three accessible date-input components, implemented on @internationalized/date (value layer) and Base UI (Popover) with hand-rolled segmented-input and calendar-grid behaviour:

    • DateField — segmented date/time input with label, description, and error message
    • DatePicker — date field with a popover calendar
    • Calendar — standalone calendar grid

    All three accept LocalizedString labels/descriptions and resolve locale + timezone from the AppShell context. The @internationalized/date value types (CalendarDate, CalendarDateTime, ZonedDateTime, …) and helpers (today, parseDate, getLocalTimeZone, …) are re-exported from @tailor-platform/app-shell.

    New AppShell context hooks:

    • useResolvedLocale() — full BCP-47 locale (e.g. "en-GB") plus the language code
    • useTimeZone() — the configured IANA timezone, falling back to the user's local timezone

    AppShell now accepts an optional timeZone prop.

    This is the @internationalized/date + Base UI variant — the lighter foundation tracked in the design proposal (§9). Net-new dependency is just @internationalized/date (~11 KB gz); Base UI is already in the bundle. Public API and accessibility contract are identical to the react-aria variant.

    Known limitation: the segmented input is built from role="spinbutton" elements that aren't contentEditable, so on-screen-keyboard typing on touch devices is limited — the calendar popover is the touch-friendly path (desktop keyboard entry works fully). The APG behaviour is unit-tested but not yet screen-reader-audited.

@github-actions github-actions Bot requested a review from a team as a code owner July 3, 2026 06:28
@github-actions github-actions Bot force-pushed the changeset-release/main branch from 54fe7c1 to cb0f612 Compare July 3, 2026 06:55
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.

0 participants