fix: element-plus styles

[likui628]

closes #4201

Description

element-plus css变量数字越大越浅，之前写反了

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Checklist

ℹ️ Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

• If you introduce new functionality, document it. You can run documentation with pnpm run docs:dev command.
• Run the tests with pnpm test.
• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Summary by CodeRabbit

• New Features

  • Introduced a new stylesheet for the ele module, enhancing style management.
  • Added custom styling for card components, ensuring consistent design.

• Improvements

  • Expanded color palette for UI themes, improving visual fidelity and accessibility.

• Bug Fixes

  • Enhanced control over styling properties to ensure uniform application across elements.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 219b40c

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

[coderabbitai]

Walkthrough

The recent changes enhance the styling capabilities of the application by introducing a new style module and expanding design tokens for colors. This results in improved visual fidelity and consistency across components, particularly the card design. The modifications align with user feedback on aesthetics and functionality, ensuring a better user experience.

Changes

File/Directory	Change Summary
apps/web-ele/src/bootstrap.ts	Added import for @vben/styles/ele to enhance styling options.
packages/effects/hooks/src/use-design-tokens.ts	Updated useElementPlusDesignTokens to expand color variables for improved design flexibility and UI accessibility.
packages/styles/package.json	Added new "./ele" module with default stylesheet path for modular style management.
packages/styles/src/ele/index.css	Introduced .el-card class with custom property for border radius, ensuring consistent design across card elements.

Assessment against linked issues

Objective	Addressed	Explanation
Ensure consistent card styling (#[4201])	✅
Improve design token management (#[4201])	✅
Fix Element Plus card corner matching (#[4201])	❓	Unclear if the styling changes resolve this.

🐇 In the meadow where colors blend,
A card with style on which we depend.
With rounded edges and shades so bright,
Our UI dances in the soft daylight.
Hooray for tokens and styles anew,
A lovely change for me and you! 🌼

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 4d7e6bb and f424ed9.

Files selected for processing (4)

• apps/web-ele/src/bootstrap.ts (1 hunks)
• packages/effects/hooks/src/use-design-tokens.ts (1 hunks)
• packages/styles/package.json (1 hunks)
• packages/styles/src/ele/index.css (1 hunks)

Files skipped from review due to trivial changes (2)

• apps/web-ele/src/bootstrap.ts
• packages/styles/src/ele/index.css

Additional comments not posted (2)

packages/styles/package.json (1)

21-23: Addition of ./ele module is well-structured.

The new entry for the "./ele" module follows the existing pattern and enhances the modularity of the style management system. This change looks good.

packages/effects/hooks/src/use-design-tokens.ts (1)

183-225: Expanded color palette enhances design flexibility.

The expanded set of CSS variable assignments for color themes significantly improves the flexibility and customization of UI components. These changes align well with the objectives of enhancing visual fidelity.

Ensure that the getCssVariableValue function correctly retrieves the intended CSS variable values for all themes.