Release 0.4.2 — custom theme registry (#96–#125) - #158
Merged
Conversation
Capture the source spec for querya.theme.v1 parsing and theme system scaling.
Break the custom theme parser epic into concrete tasks aligned with the current architecture.
Describe the extensions manager UI and marketplace integration architecture.
Link new planning documents from the documentation index.
docs(theme): custom theme parser planning (#96)
Document required fields, color formats, key mappings, fallback rules, and examples for the native Querya theme format. Closes #96.
Point VS Code import docs and the docs index to theme-custom-json.md.
docs(theme): querya.theme.v1 custom JSON schema (#96)
Add dark, light, minimal, invalid, and JSONC theme files for upcoming manifest and factory tests. Closes #97.
Parse querya.theme.v1 JSON/JSONC into an immutable manifest with shadcn/editor color maps and tokenColors, without building Flutter Color objects yet.
Cover valid fixtures, JSONC, empty color maps, validation errors, and unmodifiable maps. Closes #98.
Use const for the static QueryaThemeManifestParseException message.
feat(theme): QueryaThemeManifest parser (#98)
Normalize Querya custom hex strings and delegate 3/4/6-digit values to parseVsCodeColor; parse 8-digit AARRGGBB alpha-first colors directly.
…rser feat(theme): parseQueryaThemeColor wrapper (#99)
Add colorSchemeFromQueryaThemeColors with parseQueryaThemeColor parsing, fallback to QueryaTheme.colorScheme, and debug logs for unknown/invalid keys.
Shadcn still exposes the legacy field; keep mapping querya.theme.v1 key with targeted ignore comments for read and constructor use.
Dart ignore comments only apply to the immediately following line.
…cheme feat(theme): map shadcn_colors to ColorScheme (#100)
Add editorThemeFromQueryaColors with parseQueryaThemeColor parsing and fallback to the preset editor theme; ignore workbench keys for TP-07.
…from-manifest feat(theme): map editor_colors to QueryaEditorTheme (#101)
Add workbenchThemeFromQueryaColors for chrome/git tokens in editor_colors; ignore editor syntax keys and do not auto-map background to canvas.
…me-from-manifest feat(theme): map editor_colors to QueryaWorkbenchTheme (#102)
Wire shadcn/editor/workbench mappers into queryaThemeFromManifest, apply tokenColors to the editor, and preserve manifest syntax rules on QueryaTheme.
…s-picker TP-28: Performance test for 50+ themes in picker
TP-29: End-to-end theme import test
TP-30: Release docs and QA checklist for custom themes
Bump version to 0.4.2, finalize changelog for the custom theme registry epic, and document deferred TP-F1–F4 work for 0.4.3.
chore(release): prepare 0.4.2 and plan 0.4.3 theme follow-ups
Keep dev at 0.4.1+7 so the post-merge Auto Version Bump workflow sets 0.4.2+8 on main, matching the 0.4.1 release flow.
ZhuchkaTriplesix
added
theme
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
devfor 0.4.2 — custom theme registry epic (TP-01–TP-30, issues TP-01 — Document Querya custom theme JSON schema #96–TP-30 — Release docs and QA checklist for custom themes #125).querya.theme.v1+ VS Code JSON/JSONC scan, Theme picker (50+), import/refresh, built-in Cyberpunk Neon, startup fallback, window chrome sync.pubspec.yamlat 0.4.1+7 so the post-merge Auto Version Bump workflow sets 0.4.2+8 onmain.After merge
0.4.2+8onmain.git tag 0.4.2 && git push origin 0.4.2(triggers Release workflow).Test plan
flutter analyze— cleanflutter test --concurrency=1— green