refactor!: drop the last backward-compat token alias (pre-1.0) - #349
Conversation
SLASHED is pre-1.0 and keeps no backward-compat aliases. Removed --sf-color-text--on-surface (a pure compat alias → --sf-color-text--on-base with zero consumers). Audited the full token graph: this was the only naming-compat alias. The slashed.legacy layer (optional/legacy.css) is browser fallbacks (dvh/scrollbar), not API aliases — kept. --sf-color-surface and --sf-color-text--on-base are systematic semantic tokens — kept. Use --sf-color-text--on-base. Updated tests (on-color contrast families), token-annotations, CHANGELOG, migration guide; regenerated snapshot (693) and all docs. Full pipeline green: lint, artifacts, node 17/17, configurator 355/355, Playwright 387/387. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KPiT715ntbZQjooc3JdQAH
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (14)
💤 Files with no reviewable changes (3)
📝 WalkthroughWalkthroughThe ChangesRemove --sf-color-text--on-surface compat alias
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
Follow-up to #344 (merged). That PR shipped the v0.6.0 token-surface reduction; this is the one change that landed on the branch after the merge.
What
SLASHED is pre-1.0 and keeps no backward-compat aliases. This removes the last one:
--sf-color-text--on-surface— a pure compat alias (/* compat alias → base */) forwarding to--sf-color-text--on-base, with zero consumers. Use--sf-color-text--on-base.I audited the full token graph for other naming-compat aliases — this was the only one. (The
slashed.legacylayer inoptional/legacy.cssis browser fallbacks — dvh/scrollbar — not API aliases, so it stays.--sf-color-surfaceand--sf-color-text--on-baseare systematic semantic tokens, kept.)Changes
core/tokens.css: remove the alias.tests/tokens.spec.js: the on-color WCAG-AA contrast check listedsurface; swapped tobase(both--sf-color-baseand--on-baseresolve).docs/token-annotations.json, CHANGELOG,docs/migration.md: updated; regenerated snapshot (694 → 693) and all docs/index artifacts.Validation
lint:css✓ ·check-artifacts✓ ·api-index-sync9/9 ✓tokens+token-apigreen; full suite was 387/387 on the source branch before the cherry-pickmainproduced no drift🤖 Generated with Claude Code
Generated by Claude Code
Summary by cubic
Removed the pre-1.0 compat alias
--sf-color-text--on-surfacein favor of--sf-color-text--on-base, and updated tests/docs to reflect the change. Public token count drops from 694 to 693.--sf-color-text--on-surfacewith--sf-color-text--on-base.Written for commit 5b4c201. Summary will update on new commits.
Summary by CodeRabbit
Breaking Changes
--sf-color-text--on-surfacetoken alias. Migrate to--sf-color-text--on-base.