feat(tree): Support better customization with semantic classNames/styles as function#54988
feat(tree): Support better customization with semantic classNames/styles as function#54988thinkasany merged 7 commits intoant-design:nextfrom meet-student:tree
Conversation
|
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Note Other AI code review bot(s) detectedCodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review. ✨ Finishing touches🧪 Generate unit tests
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. 🧪 Early access (Sonnet 4.5): enabledWe are currently testing the Sonnet 4.5 model, which is expected to improve code review quality. However, this model may lead to increased noise levels in the review comments. Please disable the early access features if the noise level causes any inconvenience. Note:
Comment |
There was a problem hiding this comment.
Summary of Changes
Hello @meet-student, I'm Gemini Code Assist1! 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 significantly improves the Tree component's styling flexibility by allowing developers to define classNames and styles dynamically using functions that receive component props. This change enables more adaptive and context-aware visual presentations for tree elements, making the component more versatile for various application needs.
Highlights
- Enhanced Customization for Tree Component: The
Treecomponent now supports more flexible customization of its semantic DOM elements. TheclassNamesandstylesprops can now accept functions, allowing dynamic styling based on the component's current props (e.g.,disabled,showIcon). - Updated TreeProps Definition: The
TreePropsinterface has been refactored to incorporateBaseTreeProps, enabling the new function-basedclassNamesandstylestypes. This change allows for more powerful and contextual styling. - Dynamic Styling Logic: The
useMergeSemantichook within theTreecomponent now passes themergedProps(includingdisabledstate) to theclassNamesandstylesfunctions, facilitating conditional styling based on the component's state. - New Demo and Documentation: A new demo (
style-class.tsx) has been added to showcase both static and function-basedclassNamesandstylesusage. The API documentation (English and Chinese) has been updated to reflect these new customization capabilities. - Comprehensive Test Coverage: New test cases have been introduced to verify the correct application of both static and function-based
classNamesandstyles, ensuring the robustness of the new customization features.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| 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 issue 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
-
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. ↩
There was a problem hiding this comment.
Code Review
This pull request introduces a valuable enhancement to the Tree component, allowing classNames and styles to be provided as functions for more dynamic customization. The implementation is solid, and the new functionality is well-documented and demonstrated. I've provided a few suggestions to improve test coverage, code clarity, and documentation accuracy. Overall, great work on this feature!
👁 Visual Regression Report for PR #54988 Failed ❌
Important There are 4 diffs found in this PR: 🔄
|
More templates
commit: |
Bundle ReportChanges will decrease total bundle size by 7.91MB (-67.79%) ⬇️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: antd.min-array-pushAssets Changed:
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## next #54988 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 798 798
Lines 14747 14748 +1
Branches 3897 3897
=========================================
+ Hits 14747 14748 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Pull Request Overview
This PR adds support for better customization of the Tree component by allowing classNames and styles props to be either objects or functions. When used as functions, they receive component props as parameters, enabling dynamic styling based on the tree's state.
- Enhanced the Tree component to support function-based
classNamesandstylesfor dynamic customization - Added comprehensive test coverage for both static and function-based semantic styling
- Created documentation and demo showing the new functionality
Reviewed Changes
Copilot reviewed 8 out of 8 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| components/tree/Tree.tsx | Core implementation adding function support for classNames/styles with proper typing |
| components/tree/demo/style-class.tsx | Demo showcasing both object and function-based styling approaches |
| components/tree/demo/style-class.md | Documentation for the new styling feature |
| components/tree/index.en-US.md | English API documentation updates |
| components/tree/index.zh-CN.md | Chinese API documentation updates |
| components/tree/tests/index.test.tsx | Test coverage for semantic DOM styling functionality |
| components/tree/tests/snapshots/* | Updated test snapshots for the new demo |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.








中文版模板 / Chinese template
🤔 This is a ...
🔗 Related Issues
💡 Background and Solution
📝 Change Log