Should Temporal ship a TAI and/or GPS time zone? (or document how to build in a cookbook sample?)
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 3.7k
- Forks
- 177
- PR merge metrics
- No merged PRs in 30d
Description
While fielding replies to my tweet about https://yourcalendricalfallacyis.com/ , I noticed that @ryzokuken had already built a custom time zone for TAI, which (as I naively understand it) is the same as UTC but without leap seconds. https://github.com/ryzokuken/temporal-tai/blob/master/index.mjs
It seems like a fairly simple implementation. Should Temporal ship with a TAI time zone (or also a GPS time zone?) so folks who want better leap second support can get it without rolling their own?
If not, are these two good candidates for cookbook samples?
BTW, there was already some feedback about this a while ago: https://github.com/tc39/proposal-temporal/issues/133
I admit I don't know much about leap seconds (@gibson042 knows a lot more) so this may not be a helpful suggestion-- but at least wanted to capture it here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the linked custom implementation in index.mjs and the earlier feedback in issue 133, then compare those with Temporal's existing time-zone design. Done means reaching a documented decision about shipping TAI/GPS support or adding cookbook samples, with the chosen scope recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100