Skip to content

feat: allow expressions for all simple preset style properties #210 - #288

Draft
Julusian wants to merge 1 commit into
mainfrom
feat/preset-style-expressions
Draft

Julusian wants to merge 1 commit into
mainfrom
feat/preset-style-expressions

Conversation

@Julusian

@Julusian Julusian commented Nov 1, 2026

Copy link
Copy Markdown
Member

Each property of a simple preset's style can now be given as a plain value or as an { isExpression, value } wrapper, matching how preset option values work. textExpression is kept for backwards compatibility but is deprecated.

Needs some thought on if this is a safe approach to go with

Each property of a simple preset's `style` can now be given as a plain value or as an `{ isExpression, value }` wrapper, matching how preset option values work. `textExpression` is kept for backwards compatibility but is deprecated.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Nov 1, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

This branch has not been deployed

No deployments
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