opentiny / tiny-vue

TinyVue is an enterprise-class UI component library of OpenTiny community, support both Vue.js 2 and Vue.js 3, as well as PC and mobile.
https://opentiny.design/tiny-vue
MIT License
1.67k stars 266 forks source link

feat: optimize theme style variables #2157

Closed zzcr closed 1 month ago

zzcr commented 1 month ago

PR

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

Other information

Summary by CodeRabbit

coderabbitai[bot] commented 1 month ago

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

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 f03a590a1d2ecef1f5f8042e3bc2d31094b2a138 and b26e848593eabbfefba3a6a4ad80de23a8fb1e14.
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](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)
Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: -- `I pushed a fix in commit , 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.
github-actions[bot] commented 1 month ago

[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