feat(collapse): [collapse] fix style issues in the old theme

[wuyiping0628]

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 the background color of the CollapseItem component for improved visual design.

[coderabbitai]

Walkthrough

The changes in this pull request involve modifying a LESS stylesheet for the CollapseItem component. The primary alteration is the update of the background color variable from var(--tv-color-bg) to var(--tv-color-bg-gray-1), which affects the visual styling of the component.

Changes

File Path	Change Summary
packages/theme/src/collapse-item/vars.less	Updated the background color variable --tv-CollapseItem-bg-color from var(--tv-color-bg) to var(--tv-color-bg-gray-1) in the .inject-CollapseItem-vars() function.

Possibly related PRs

• refactor(collapse): [collapse] refactor collapse theme vars #2201: Refactors the CollapseItem component's theme variables, including changes to the vars.less file where the --tv-CollapseItem-bg-color variable is defined.
• fix(theme): update vars.less comments #2160: Updates comments in the vars.less file, relevant to the overall theme variable organization and documentation.
• fix(theme): remove oldTheme's DOCS #2417: Focuses on removing documentation related to the old theme, which may relate to theme management and variable usage.

Suggested labels

enhancement

Suggested reviewers

• zzcr

Poem

In the meadow where colors play,
A rabbit hops, brightening the day.
With a change to the CollapseItem hue,
Gray-1 shines, a fresh debut!
Hooray for styles that dance and twirl,
In our theme, let colors swirl! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between af3d194 and db460e0.

📒 Files selected for processing (1)

• packages/theme/src/collapse-item/vars.less (1 hunks)

🔇 Additional comments (1)

packages/theme/src/collapse-item/vars.less (1)

17-17: LGTM! Consider verifying the visual impact.

The change from --tv-color-bg to --tv-color-bg-gray-1 for the collapse item's background color is appropriate and aligns with the PR's objective of fixing style issues in the old theme.

Let's verify if this color variable is consistently defined across themes:

✅ Verification successful

The color variable change is safe and well-defined

The verification shows that --tv-color-bg-gray-1 is properly defined in the base theme files (old-theme.less and vars.less) and is consistently used across multiple components including upload-dragger, numeric, hrapprover, grid, and collapse-item. The variable is defined as:

--tv-color-bg-gray-1: var(--tv-base-color-common-2); // #fafafa 灰色背景-1：灰色卡片背景色/表格下展背景色

This confirms that the change aligns with the existing design system and follows the established pattern for gray background colors in the theme.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check if --tv-color-bg-gray-1 is defined in theme files
# and ensure it's not causing any undefined variable issues

# Search for the color variable definition
echo "Searching for color variable definition:"
rg --type=less "tv-color-bg-gray-1"

# Check for potential undefined variable warnings in build logs
echo "Checking for any undefined variable warnings:"
rg --type=log "tv-color-bg-gray-1.*undefined"

Length of output: 1163

---

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.