feat: optimize theme style variables

[zzcr]

PR

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our Commit Message Guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

• New Features

  • Updated CSS variable naming conventions for better clarity and consistency across the theme.
  • Enhanced styling for input components, ensuring adherence to new design specifications.

• Bug Fixes

  • No bug fixes were included in this release.

• Chores

  • Systematic renaming of CSS custom properties to improve maintainability and readability without altering functionality.

[coderabbitai]

Walkthrough

The pull request involves a systematic renaming of CSS custom properties across various LESS files to enhance naming consistency and clarity. The prefixes for color and input-related variables have been standardized from --tv-common- and --ti- to --tv-. This change affects multiple variables related to colors, fonts, borders, and sizes, while maintaining the original functionality and structure of the styles. The modifications focus on improving code maintainability and readability without altering the visual representation of components.

Changes

File Path	Change Summary
packages/theme/src/base/vars.less	Renamed CSS custom properties to standardize naming conventions, changing prefixes from --tv-common- to --tv-.
packages/theme/src/input/index.less	Updated CSS variables from --ti- to --tv-, ensuring consistency in input component styling.
packages/theme/src/input/vars.less	Renamed input-related CSS custom properties from --ti- to --tv-, enhancing naming consistency.

Possibly related PRs

• fix(input): [input] fix textarea x-design style #2076: Renaming CSS variables in the input component aligns with the changes in the main PR.
• feat(button): [button] Adapting to the SMB theme #2079: Updates to button styles relate to the overall theme changes consistent with the main PR.
• feat(button): [button] Adapting to the SMB theme #2104: Modifications to button styles reflect similar standardization efforts as seen in the main PR.
• feat(badge): [badge] Adapting to the SMB theme #2107: Badge component changes focus on adapting to the SMB theme, parallel to the main PR's updates.
• feat(drop-times): [drop-times] Adapting to the SMB theme #2118: Picker component changes aim to align with the SMB theme, consistent with the main PR's objectives.
• feat(button): [button] Adapting to the SMB theme #2120: Button styles and variable updates align with the main PR's standardization efforts.
• fix(theme):　[tree,tooltip,transfer, cascader] update unsolved smb components #2124: Modifications to various components address theme-related issues, consistent with the main PR's focus.
• feat: [input] add new vars less #2128: Introduction of new variables supports theme standardization efforts seen in the main PR.
• feat(checkbox): [checkbox] Adapting to the SMB theme #2130: Checkbox component changes reflect adaptation to the SMB theme, consistent with the main PR.
• feat(dialog-box): [dialog-box] modify smb theme #2147: Dialog box modifications focus on theme adjustments, paralleling the main PR's changes.
• feat(button): [button] Adapting to the SMB theme #2148: Button component changes aim to align with the SMB theme, a key focus of the main PR.
• feat(carousel): [carousel] modify smb theme #2153: Carousel component updates aim to modify the SMB theme, aligning with the main PR's objectives.

Suggested labels

enhancement

Poem

🐇 In the garden of code, we hop and play,
With colors and styles, we brighten the day.
Renaming our variables, a tidy delight,
Consistency blooms, making everything right.
So here's to our changes, both clever and bright,
A theme that unites, in the soft morning light! 🌼

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between f03a590 and b26e848.

Files selected for processing (3)

• packages/theme/src/base/vars.less (3 hunks)
• packages/theme/src/input/index.less (10 hunks)
• packages/theme/src/input/vars.less (1 hunks)

Files skipped from review due to trivial changes (2)

• packages/theme/src/base/vars.less
• packages/theme/src/input/vars.less

Additional comments not posted (13)

packages/theme/src/input/index.less (13)

26-26: LGTM!

The change is consistent with the overall theme variable renaming and the usage is correct.

---

31-31: LGTM!

The changes are consistent with the overall theme variable renaming and the usage is correct.

Also applies to: 34-34

---

40-43: LGTM!

The changes are consistent with the overall theme variable renaming and the usage is correct.

---

57-57: LGTM!

The change is consistent with the overall theme variable renaming and the usage is correct.

---

67-67: LGTM!

The change is consistent with the overall theme variable renaming and the usage is correct.

---

73-73: LGTM!

The change is consistent with the overall theme variable renaming and the usage is correct.

---

78-78: LGTM!

The change is consistent with the overall theme variable renaming and the usage is correct.

---

83-83: LGTM!

The changes are consistent with the overall theme variable renaming and the usage is correct.

Also applies to: 86-86, 89-89

---

99-100: LGTM!

The changes are consistent with the overall theme variable renaming and the usage is correct.

Also applies to: 104-104

---

110-110: LGTM!

The change is consistent with the overall theme variable renaming and the usage is correct.

---

116-123: LGTM!

The changes are consistent with the overall theme variable renaming and the usage is correct.

Also applies to: 129-129

---

135-135: LGTM!

The changes are consistent with the overall theme variable renaming and the usage is correct.

Also applies to: 139-139, 152-152, 156-156, 161-161, 167-167, 172-172, 183-183, 189-189, 196-196, 204-204, 207-210, 213-213

---

230-231: LGTM!

The changes are consistent with the overall theme variable renaming and the usage is correct.

Also applies to: 235-236, 250-250, 252-252, 257-257, 259-259, 264-264, 266-266, 290-290, 345-348

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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.
  -- Generate unit testing code for this file.
  • 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. Examples:
  -- @coderabbitai generate unit testing code for this file.
  -- @coderabbitai modularize this function.
• 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 src/utils.ts and generate unit testing code.
  -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

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

Documentation and Community

• 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.

[github-actions]

[e2e-test-warn]
The component to be tested is missing.

The title of the Pull request should look like "fix(vue-renderless): [action-menu, alert] fix xxx bug".

Please make sure you've read our contributing guide