docs: clarify local-time semantics of anchor dates - #50
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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
1 participant
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.
The docs now spell out the timezone contract for anchor dates: the controlled
dateprop is read in the device's local time zone, so a UTC-midnight instant falls on the previous local day west of UTC and builds the wrong week. The time-zones guide gains an "Anchor dates are local" section with that repro, the API reference notes it on thedaterow, and both renderers'dateprop now documents it in JSDoc so the contract surfaces in editor tooltips. Normalizing internally instead was rejected:startOfDaykeeps a UTC-midnight instant on the previous local day, and a heuristic that reinterprets such instants as date-only values would silently change paging for existing callers.Closes #49