chore: add more cls

[zombieJ]

Summary by CodeRabbit

发布说明

• 样式改进

  • 优化了搜索输入时的样式处理，提供更精确的样式控制。
  • 增强了自定义选项样式的应用机制。

• 测试

  • 新增搜索状态相关的样式测试。
  • 新增选项自定义样式的测试覆盖。

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
select	Ready	Preview, Comment	Jan 30, 2026 2:30pm

[coderabbitai]

Caution

Review failed

The pull request is closed.

概览

该PR为SingleContent.tsx的根容器添加了两个条件CSS类（mergedSearchValue和hasOptionStyle），并在测试文件中添加了两个相应的测试用例，用于验证这些样式类的应用场景。

变化

内聚类/文件	总结
样式类条件渲染 src/SelectInput/Content/SingleContent.tsx	添加两个新的条件CSS类：mergedSearchValue（当存在搜索值时应用）和hasOptionStyle（当显示选项提供自定义className或style时应用）。
测试验证 tests/Select.test.tsx	新增两个测试用例：验证showSearch启用时搜索输入是否应用-content-has-search-value类名；验证Option包含内联样式时是否应用-content-has-option-style类名。

预估代码审查工作量

🎯 2 (Simple) | ⏱️ ~10 minutes

可能相关的PR

• refactor: Simplify Select single structure #1195: 同样修改SingleContent.tsx文件中的样式和渲染逻辑，涉及hasOptionStyle和mergedSearchValue相关的样式应用。
• feat: add more semantic structure #1168: 同样修改SingleContent.tsx中的className使用方式，涉及content相关的classNames和styles支持。

建议审查人员

• meet-student

诗

🐰 搜索值闪烁，样式迎风摇，
两行新类名，测试来证照，
条件若触发，容器换新衣，
优雅的细节，代码齐整齐！✨

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch more

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @zombieJ, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the SelectInput component by adding new CSS classes that provide more granular styling control. These classes are dynamically applied based on the component's internal state, specifically when a search value is active or when a selected option has custom inline styles. This change allows for more flexible and targeted styling adjustments, ensuring a better user experience and design consistency.

Highlights

• New CSS Classes for SelectInput: Introduced two new conditional CSS classes to the SingleContent component: rc-select-content-has-search-value and rc-select-content-has-option-style.
• Conditional Application: The rc-select-content-has-search-value class is applied when a search value is present (mergedSearchValue), and rc-select-content-has-option-style is applied when the selected option has custom styling (hasOptionStyle).
• Enhanced Test Coverage: Added new tests in Select.test.tsx to verify the correct application of these new classes under their respective conditions.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.43%. Comparing base (c7b5499) to head (ed2f233).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1196   +/-   ##
=======================================
  Coverage   99.42%   99.43%           
=======================================
  Files          31       31           
  Lines        1227     1229    +2     
  Branches      439      441    +2     
=======================================
+ Hits         1220     1222    +2     
  Misses          7        7           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[gemini-code-assist]

Code Review

This pull request adds two new CSS classes, -content-has-search-value and -content-has-option-style, to the SingleContent component to provide more styling hooks. The changes are accompanied by new tests. My review found an issue in one of the new tests which appears to be testing existing behavior rather than the newly added class. I've suggested a correction to the test to ensure the new functionality is properly covered.