fix: vben tree component warning

[mynetfan]

Description

修复VbenTree组件产生的警告

fix: #5807

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Checklist

ℹ️ Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

• If you introduce new functionality, document it. You can run documentation with pnpm run docs:dev command.
• Run the tests with pnpm test.
• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Summary by CodeRabbit

• Style
  • Improved the visual layout by refining container styling for key UI components.
  • Enhanced transition effects to deliver smoother visual animations during interactions.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9dd9dab

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

The changes update the styling in the tree component by adjusting class attributes. The TreeRoot now includes the container class, while the TransitionGroup component has had its explicit container class removed. There are no modifications to the exported or public entities, and the adjustments focus solely on component appearance and structure.

Changes

File(s)	Change Summary
packages/@core/ui-kit/.../tree/tree.vue	Added the container class to the TreeRoot component and removed the explicit container class from the TransitionGroup component.

Assessment against linked issues

Objective	Addressed	Explanation
Bug: 角色页面新增或修改时，树结构控制台警告 (#5807)	✅

Possibly related PRs

• vbenjs/vue-vben-admin#5794: Modifies properties and event handling in the same tree component, indicating a direct code-level connection.

Suggested labels

bug

Suggested reviewers

• anncwb
• jinmao88
• vince292007

Poem

I'm a little rabbit, hopping through the code,
Tweaks in the tree make the warnings erode,
Classes now aligned, a subtle design,
With each gentle change, our UI will shine,
Crunching carrots and bugs—what a joyful mode!

---

📜 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 3c2d325 and 9dd9dab.

📒 Files selected for processing (1)

• packages/@core/ui-kit/shadcn-ui/src/ui/tree/tree.vue (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (5)

• GitHub Check: Test (windows-latest)
• GitHub Check: Lint (windows-latest)
• GitHub Check: Check (windows-latest)
• GitHub Check: post-update (ubuntu-latest)
• GitHub Check: post-update (windows-latest)

🔇 Additional comments (2)

packages/@core/ui-kit/shadcn-ui/src/ui/tree/tree.vue (2)

213-213: Addition of "container" class to TreeRoot component resolves styling issue

The "container" class has been added to the TreeRoot component, which appropriately moves the styling from the TransitionGroup to its parent. This change ensures that the positioning and layout are controlled at the right level in the component hierarchy.

---

222-222: Removed unnecessary class from TransitionGroup component

Removing the "container" class from the TransitionGroup component is the correct approach to address the warning mentioned in issue #5807. TransitionGroup components in Vue can sometimes generate warnings when directly styled with positioning classes, as they have specific requirements for their transition animations to work properly.

---

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

🪧 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 plan to trigger planning for file edits and PR creation.
• @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.