Repository navigation
docs(theme): sync each theme as one record at the oldest schema that holds it - #4203
Merged
Merged
Conversation
datlechin
enabled auto-merge (squash)
November 11, 2026 15:46
datlechin
disabled auto-merge
November 11, 2026 15:54
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.
Summary
theme.md, Sync: back to one record per theme,theme.<id>, encoded at the oldest schema that holds its keys.data-sync-storage.md: the exception covers the synced record too.The split-record design (#4188 to #4198) kept producing new sync defects in review, so the grid type colors PR ships the single record and states the limit. Replaces the Sync text of #4188, #4193, #4195, #4197 and #4198.
Test plan
Docs only. The code and its tests land in the grid type colors PR.