Skip to content

feat(date/time): use Temporal API#166

Draft
logaretm wants to merge 4 commits into
mainfrom
feat/use-temporals
Draft

feat(date/time): use Temporal API#166
logaretm wants to merge 4 commits into
mainfrom
feat/use-temporals

Conversation

@logaretm

@logaretm logaretm commented Apr 1, 2025

Copy link
Copy Markdown
Member

What

This PR migrates the current date/time fields implementation to use Temporal API, I won't merge this yet as I want to frontload this when the time is right to do so.

For now, I will use the fullcalendar polyfill

I also would like to take advantage of the specialized types available in the Temporal API like PlainTime for time fields as a value and PlainDate for calendars if it makes sense.


Blocked by

microsoft/TypeScript#60164
nodejs/node#57127

@changeset-bot

changeset-bot Bot commented Apr 1, 2025

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: b466f96

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@logaretm logaretm force-pushed the feat/use-temporals branch from 4c12f23 to ea121ec Compare April 1, 2025 02:50
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