chore: sparkle-design-cli 2.4.1 で sparkle-design.css を再生成#289
Conversation
@theme inline のセマンティック宣言をプリミティブ直接参照から自己参照に変更する 不具合修正(goodpatch/sparkle-design-internal#229 フォローアップ、 sparkle-design-cli v2.4.1)を取り込む。生成物のみの変更で、デフォルト表示 (属性スコープでの上書きを使わない現状の運用)には影響しない (Storybook で Button/Switch/Tabs をピクセル差分ゼロで確認済み)。 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 59 seconds Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Pull request overview
sparkle-design-cli v2.4.1 の修正(@theme inline のセマンティック宣言がプリミティブ直参照になってしまう問題)に追従して、sparkle-design.css の Tailwind v4 用トークン定義を再生成し、ランタイム上書き可能なセマンティック変数参照を維持するための更新です。
Changes:
@theme inline内のセマンティックトークンを、プリミティブ直参照から「同名のセマンティック変数の自己参照」に変更- 変更理由と Tailwind v4 のインライン化挙動に関する説明コメントを追加
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 985930e352
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| --color-primary-200: var(--color-primary-200); | ||
| --color-primary-300: var(--color-primary-300); | ||
| --color-primary-400: var(--color-primary-400); | ||
| --color-primary-500: var(--color-primary-500); |
There was a problem hiding this comment.
Avoid publishing self-referential registry theme vars
When make registry runs, scripts/build-sparkle-design-theme.mjs reads the @theme inline block and merges those declarations over the first :root block before writing sparkle-design-theme.json; with this self-reference pattern, the generated registry theme contains entries like color-primary-500: var(--color-primary-500). Registry consumers receive only those cssVars, so the variable is defined in terms of itself and semantic colors/radii/shadows become unresolved even though importing the full CSS in this app still works.
Useful? React with 👍 / 👎.
@theme inline 自己参照コメントを簡潔にし、社内 issue 番号への言及を削除した sparkle-design-cli v2.4.2 を反映。生成される CSS は公開 npm パッケージにも 同梱され消費側の CSS にそのまま出力されるため、社内 issue 番号を含めるべき ではなかった。 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Summary
sparkle-design-cliv2.4.1(goodpatch/sparkle-design-cli#69)で@theme inlineのセマンティック宣言をプリミティブ直接参照から自己参照に変更する不具合修正が入ったため、sparkle-design.cssを再生成影響
@theme inlineブロックの内部参照方法のみ)。現状の運用(属性スコープでの上書きを使わない default 表示)には一切影響しませんbbox=None, max_channel_diff=0)Co-Authored-By: Claude Sonnet 5 noreply@anthropic.com