refactor(theme): Use assignInlineVars for theme variable binding

[froggy1014]

Changes

ThemeProvider에서DOM 조작 방식을 선언형 contract 시스템으로 변경했습니다.

@vanilla-extract/dynamic의 assignInlineVars를 사용하여 Vanilla Extract의 contract 시스템을 그대로 쓸 수 있게됩니다.

• 수동 CSS 변수명(--side-color-primary)이 contract 정의와 일치하지 않음

// tokens/src/theme/contract.ts - Contract 정의
export const vars = createGlobalThemeContract({
  color: {
    primary: 'color-primary',
    background: 'color-background'
  }
}, (value) => `side-${value}`);
// 실제 생성되는 CSS 변수: --side-color-primary, --side-color-background

// theme/src/ThemeProvider.tsx - 기존 방식 (문제)
useEffect(() => {
  if (containerRef.current) {
    Object.entries(theme).forEach(([key, value]) => {
      // 여기서 설정하는 변수명과 contract가 다름
      containerRef.current?.style.setProperty(`--side-color-${key}`, value);
      //                                        ^^^^^^^^^^^^^^^^
      //                                        예: --side-color-primary
    });
  }
}, [theme]);

// button/src/Button.css.ts - CSS에서 사용 (문제)
[ButtonVariant.filled]: {
  // Contract 참조와 하드코딩된 변수명이 혼재
  backgroundColor: vars.color.primary,           // ← Contract 참조
  color: `var(--side-color-background, black)`, // ← 하드코딩된 변수명
  //           ^^^^^^^^^^^^^^^^^^^^^^
  //           수동으로 작성한 변수명이 contract와 일치한다는 보장 없음
}

---

// theme/src/ThemeProvider.tsx - assignInlineVars 사용
const themeVars = assignInlineVars(vars.color, theme);
// Contract와 theme 값을 자동으로 매핑

[changeset-bot]

⚠️ No Changeset found

Latest commit: b46aabb

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

💥 An error occurred when fetching the changed packages and changesets in this PR

Some errors occurred when validating the changesets config:
The package or glob expression "@sipe-team/package-name" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.

[netlify]

✅ Deploy Preview for side-design-system ready!

Name	Link
🔨 Latest commit	b46aabb
🔍 Latest deploy log	https://app.netlify.com/projects/side-design-system/deploys/68a87b40a4ee330008f4e3cb
😎 Deploy Preview	https://deploy-preview-200--side-design-system.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch refactor/theme-provider-assign-vars

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

Files with missing lines	Coverage Δ
packages/theme/src/ThemeProvider.tsx	100.00% <100.00%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.