Skip to content

Conversation

@kavhnr
Copy link

@kavhnr kavhnr commented Aug 20, 2025

Name of theme

Zed One Dark and Zed One Light

How Has This Been Tested?

✅ Generated preview images using python3 ./scripts/gen_theme_previews.py standard

Contributing Guidelines Checklist

  • Forked the project
  • Created feature branch with theme/ prefix format
  • All colors in hex format starting with #
  • No custom background images included
  • Files added to standard/ directory
  • Preview images generated and committed
  • Regenerated thumbnails using required script
  • Files use snake_case naming (following existing repo patterns)

⚠️ Documentation vs Schema Conflict

Documentation states (Custom Themes docs):

"A custom theme in Warp has the following .yaml structure:"

name: Custom Theme # Name for the theme
cursor: '#95D886' # Input cursor color (optional; defaults to accent color if omitted)

However:

[ ] name field: Adding this produces error: "Property name is not allowed. (yaml-schema: warp-themes.json 513)"
[ ] cursor field: Adding this produces error: "Property cursor is not allowed. (yaml-schema: warp-themes.json 513)"

Existing themes confirmation: solarized_dark.yaml, solarized_light.yaml, and other standard themes omit both name and cursor fields.

Current approach: Followed existing theme structure and schema validation to ensure themes work properly. Please confirm if documentation needs updating or if there's a
different schema for contributed themes.

- Add zed_one_dark.yaml with proper theme structure
- Add zed_one_light.yaml with proper theme structure
- Include preview images for both themes
- Follow repository naming conventions (snake_case)
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