feat: add canonical calendar dates - #480
Open
blove wants to merge 16 commits into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
Vercel preview readyPreview: https://pretable-jrmk8310u-cacheplane.vercel.app Updated automatically by the |
blove
enabled auto-merge (squash)
August 19, 2026 04:43
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.
Summary\n\n- define one strict RFC 3339 full-date contract for date columns: YYYY-MM-DD or null\n- add canonical date sorting, filtering, grouping, distinct values, and date min/max aggregation to the incremental row model\n- add native locale-aware date formatting across cells, aggregates, copy, HTML, TSV, and CSV\n- make date editing, filtering, paste, async edit ownership, and controlled-model behavior strict and race-safe\n- publish the public API, migration guide, server-data example, changeset, and roadmap update\n\n## Why\n\nFinancial and planning applications repeatedly need date-only values that do not shift with time zones or permissive JavaScript parsing. Pretable should provide this as a general grid primitive without embedding financial-domain policy.\n\nThis is an intentional breaking correction. Date columns no longer accept Date objects, epoch numbers, date-time strings, or localized strings through built-in behavior. Applications must project those values to YYYY-MM-DD or null at their boundary.\n\n## Validation\n\n- full repository tests\n- full type checking, lint, formatting, and production builds\n- public API report checks\n- package publication and compatibility checks\n- publish preflight\n- local documentation browser tests in Chromium and WebKit\n- independent architecture and whole-branch review