Skip to content

fix(tree): [tree] elevate the priority #3119 #3284

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 2 commits into from
Apr 16, 2025
Merged

fix(tree): [tree] elevate the priority #3119 #3284

merged 2 commits into from
Apr 16, 2025

Conversation

James-9696
Copy link
Collaborator

@James-9696 James-9696 commented Apr 11, 2025

PR

修改issue单#3119,样式权重优先级,导致在tree组件嵌套使用numeric\input组件的size属性不生效

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: #3119

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Summary by CodeRabbit

  • Style
    • Updated input styling to apply only when editing a tree node, ensuring consistent appearance for edit mode inputs.
  • Refactor
    • Scoped input styles more narrowly to avoid affecting non-editable inputs within the tree component.

Copy link

coderabbitai bot commented Apr 11, 2025

Walkthrough

The changes refine the styling and class structure for editable input fields within tree nodes. The CSS selector for input styling is narrowed to only affect inputs inside a new wrapper class. Correspondingly, the Vue component now wraps the editable input with this specific class when a node is in edit mode. No logic or exported/public API was altered.

Changes

File(s) Change Summary
packages/theme/src/tree/index.less Updated input selector to .tree-node-prefix__edit-input input, narrowing styling scope.
packages/vue/src/tree/src/tree-node.vue Added tiny-tree-node__edit-input class to the edit-mode input wrapper in the tree node template.

Suggested labels

bug

Suggested reviewers

  • zzcr

Poem

In the forest of code where tree nodes grow,
A rabbit hopped by to help inputs show.
With classes refined and selectors precise,
The edit fields now look extra nice.
No more wild styles running free,
Just neat little edits, as tidy as can be! 🐇🌳

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

packages/vue/src/tree/src/tree-node.vue

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-vue".

(The package "eslint-plugin-vue" was not found when loaded as a Node module from the directory "".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-vue@latest --save-dev

The plugin "eslint-plugin-vue" was referenced from the config file in ".eslintrc.js » @antfu/eslint-config » @antfu/eslint-config-vue".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)
  • We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8491ab1 and 89ffab2.

📒 Files selected for processing (2)
  • packages/theme/src/tree/index.less (1 hunks)
  • packages/vue/src/tree/src/tree-node.vue (1 hunks)
✅ Files skipped from review due to trivial changes (2)
  • packages/vue/src/tree/src/tree-node.vue
  • packages/theme/src/tree/index.less

🪧 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 generate docstrings to generate docstrings for this 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 github-actions bot added the bug Something isn't working label Apr 11, 2025
Copy link

Walkthrough

This PR modifies the CSS selectors for input and numeric components by increasing the specificity of the medium, small, and mini size classes. This is achieved by changing single ampersand selectors to double ampersand selectors, which elevates their priority in the CSS cascade.

Changes

File Summary
packages/theme/src/input/index.less Changed &-medium, &-small, and &-mini to &&-medium, &&-small, and &&-mini to increase specificity.
packages/theme/src/numeric/index.less Changed &--medium, &--small, and &--mini to &&--medium, &&--small, and &&--mini to increase specificity.

@@ -249,19 +249,19 @@
padding-left: 8px;
}

&-medium {
&&-medium {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The change from &-medium to &&-medium increases the specificity of the CSS selector, which can affect how styles are applied if there are conflicting styles. Ensure that this change does not unintentionally override other styles.

@@ -273,7 +273,7 @@
}
}

&--medium {
&&--medium {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The change from &--medium to &&--medium increases the specificity of the CSS selector, which can affect how styles are applied if there are conflicting styles. Ensure that this change does not unintentionally override other styles.

Copy link

@coderabbitai coderabbitai bot left a 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

🧹 Nitpick comments (6)
packages/theme/src/input/index.less (3)

252-254: Increase Specificity for Medium Input Size

The selector change from a single ampersand to double (&&-medium) increases specificity for the medium input size. This should help resolve style override issues as intended in #3119. Please ensure that the increased specificity does not unintentionally override any global customizations.


256-263: Increase Specificity for Small Input Size

The replacement of &-small with &&-small similarly elevates the specificity for small-sized inputs. Verify that this change remains consistent with any external or higher-level selectors to prevent undesired style conflicts.


264-270: Increase Specificity for Mini Input Size

Using &&-mini instead of &-mini boosts the selector priority for mini size styling. Confirm that the cascade remains predictable and that no unintended side effects appear in components that rely on these styles.

packages/theme/src/numeric/index.less (3)

276-297: Elevate Specificity for Medium Numeric Input

Changing the size variant selector to &&--medium effectively increases its specificity. This should help overcome conflicts in nested CSS or lower-priority overrides. Please double-check that all related numeric components render as expected with the new selector.


299-320: Elevate Specificity for Small Numeric Input

The update from a single ampersand to double (&&--small) elevates the specificity of the small numeric input styling rules. Ensure that these rules harmonize with the overall theme and do not introduce any style breaking changes in different layout scenarios.


322-344: Elevate Specificity for Mini Numeric Input

The selector for the mini numeric input is now using &&--mini, which increases its specificity. This change aligns with the pattern used across input components. Review the rendered output to confirm that there is no unintended interference with padding or font-size adjustments.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d843901 and 8491ab1.

📒 Files selected for processing (2)
  • packages/theme/src/input/index.less (1 hunks)
  • packages/theme/src/numeric/index.less (3 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: PR E2E Test (pnpm test:e2e3)

@James-9696 James-9696 changed the title fix(numeric,input): [numeric,input] elevate the priority #3119 [wip]:fix(numeric,input): [numeric,input] elevate the priority #3119 Apr 14, 2025
@github-actions github-actions bot removed the bug Something isn't working label Apr 14, 2025
@James-9696 James-9696 changed the title [wip]:fix(numeric,input): [numeric,input] elevate the priority #3119 fix(numeric,input): [numeric,input] elevate the priority #3119 Apr 15, 2025
@github-actions github-actions bot added the bug Something isn't working label Apr 15, 2025
@James-9696 James-9696 changed the title fix(numeric,input): [numeric,input] elevate the priority #3119 fix(tree): [tree] elevate the priority #3119 Apr 16, 2025
@zzcr zzcr merged commit 84d58ed into dev Apr 16, 2025
18 of 20 checks passed
@zzcr zzcr deleted the fix-issue-3119 branch April 16, 2025 07:51
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

🐛 [Bug]: 树插槽中设置 TinyNumeric 和 TinyInput的 size 属性无法
2 participants