feat(date/time): use Temporal API#166
Draft
logaretm wants to merge 4 commits into
Draft
Conversation
|
4c12f23 to
ea121ec
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
PlainTimefor time fields as a value andPlainDatefor calendars if it makes sense.Blocked by
microsoft/TypeScript#60164
nodejs/node#57127