-
Notifications
You must be signed in to change notification settings - Fork 284
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(split): [split] fix split error apis #2377
Conversation
WalkthroughThe changes involve updates to the Changes
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (3)
examples/sites/demos/apis/split.js (1)
Line range hint
89-99
: Consider adding pcDemo reference for border propThe
border
prop is missing apcDemo
reference. Consider adding a reference to demonstrate the no-border mode functionality mentioned in the changes.packages/theme/src/split/index.less (2)
30-34
: Consider using CSS variable for border width.The no-border mode implementation is clean and straightforward. However, to maintain consistency with the theme system and improve maintainability, consider using a CSS variable for the border width.
// 无边框模式 &.no-border { - border: none; + border-width: var(--tv-Split-wrapper-border-width, 0); }
Line range hint
36-39
: Consider adding visual cues for nested splits.While removing borders and border-radius for nested splits prevents visual clutter, it might make it harder to distinguish between different nesting levels. Consider adding subtle visual cues to improve the hierarchy.
& & { border-radius: 0; border: none; + background-color: var(--tv-Split-nested-bg, rgba(0, 0, 0, 0.02)); }
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (2)
- examples/sites/demos/apis/split.js (5 hunks)
- packages/theme/src/split/index.less (1 hunks)
🔇 Additional comments (5)
examples/sites/demos/apis/split.js (5)
17-17
: LGTM: Demo reference better matches functionalityThe updated
pcDemo
value 'horizontal-collapse' better represents the collapse button functionality compared to the previous 'split-threshold'.
28-28
: LGTM: Maintains consistency with collapse-left-topThe change to 'horizontal-collapse' maintains consistency with the collapse-left-top prop and better reflects the functionality.
87-87
: LGTM: Demo reference is now self-documentingThe new
pcDemo
value 'three-areas' directly matches the feature name, making it more intuitive and self-documenting.
124-124
: LGTM: Demo reference accurately reflects event typeThe updated
pcDemo
value 'event-click' correctly represents the click event nature, fixing the previous misleading reference to 'moving-event'.
168-168
: LGTM: Maintains consistency with left-top-clickThe change to 'event-click' maintains consistency with the left-top-click event and correctly represents the event type.
PR
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information
Summary by CodeRabbit