Skip to content

fix: support named colors and single-mode theme imports (v1.2.1)#10

Merged
kkugot merged 2 commits intomainfrom
release/v1.2.1
Mar 23, 2026
Merged

fix: support named colors and single-mode theme imports (v1.2.1)#10
kkugot merged 2 commits intomainfrom
release/v1.2.1

Conversation

@kkugot
Copy link
Copy Markdown
Owner

@kkugot kkugot commented Mar 23, 2026

Summary

Fix theme import/export handling so named CSS colors and dark-only or light-only theme bundles can be released safely.


Context / Motivation

Importing some valid OpenCode themes failed because named colors like teal were not normalized and single-mode theme files were rejected unless every token declared both dark and light values.


Changes

  • add CSS named color normalization in the app and import script
  • accept combined theme token objects that provide dark, light, or both
  • merge partial JSON mode updates without overwriting the untouched mode
  • add regression coverage for named colors, dark-only imports, and light-only imports
  • bump the package version to 1.2.1

Testing

  • npm run test
  • npm run lint
  • npm run build
  • ✅ verified public/import-export.sh with dark-only and light-only named-color theme files

Version

Patch release: 1.2.1

@kkugot kkugot merged commit 288d08a into main Mar 23, 2026
1 check passed
@kkugot kkugot deleted the release/v1.2.1 branch March 23, 2026 20:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant