fix(steps): repair bar step bar small gray dots

[chenxi-20]

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

• Style
  • Updated the styling of step blocks, removing border-radius for a square appearance.
  • Adjusted hover states and background colors for improved visual feedback.
  • Maintained consistent styling for different step states: done, doing, active, and fault.

[coderabbitai]

Walkthrough

The changes in this pull request focus on the styling of the steps and timeline interface within the index.less file. Key modifications include the removal of the border-radius property from the step blocks, altering their appearance to be square. Adjustments to hover states, background colors, and the consistent use of CSS variables for colors and sizes are also made. The overall layout and flex properties remain unchanged, ensuring that the visual feedback for different step states is preserved without introducing new functionality.

Changes

File	Change Summary
packages/theme/src/steps/index.less	- Removed border-radius from .@{steps-prefix-cls}-block class. - Adjusted hover states and background colors. - Maintained structure for states like .done, .doing, .active, and .fault. - Preserved layout and flex properties for elements like .more-button and .@{steps-prefix-cls}-content. - Consistent use of CSS variables for colors and sizes.

Possibly related PRs

• feat(steps): [steps] Node line alignment #2116: Modifies the same index.less file, addressing visual aspects of the steps component.
• refactor(steps): [steps, timeline] Refactoring the steps and timeline themes #2261: Focuses on styling changes in index.less, including hover effects and layout adjustments relevant to this PR.
• fix(icon): [steps] The size of the steps icon is modified to adapt to the new specifications. #2344: Updates index.less for the steps component, specifically addressing icon sizes related to the overall styling.
• fix(e2e): [time-line] Fixing Test Cases #2407: Involves updates to the visual representation of timeline items, closely related to the changes in this PR.
• fix(tabs): [tabs] Fixed the floating issue of the close button on the tab page and the style issue of the close button under the buttoncard. #2425: Addresses styling issues in the tabs component, sharing some visual design principles with the steps component.
• test(site): fix icon not correct test e2e #2445: Modifies tests related to icon visibility, relevant to the visual aspects discussed in this PR.

Suggested reviewers

• zzcr

🐇 In the meadow where the steps align,
Borders once rounded, now square they shine.
Colors and hover, all neatly arranged,
A visual delight, though shapes have changed.
With CSS magic, the styles take flight,
A hop and a skip, all feels just right! 🌼

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between fd535ac and 762bf25.

📒 Files selected for processing (1)

• packages/theme/src/steps/index.less (0 hunks)

💤 Files with no reviewable changes (1)

• packages/theme/src/steps/index.less

---

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