fix(tree): default-expanded-keys description is wrong

[shenjunjian]

PR

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: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

• New Features
  • Updated the default-expanded-keys property in the tree component to accept an array of strings, enhancing flexibility in node expansion.
  • Improved the description of the default-expanded-keys property for better clarity on its functionality.

[coderabbitai]

Walkthrough

The pull request modifies the default-expanded-keys property in the tree component's API definition. The change transforms the property from a boolean to an array of strings, updating its type, default value, and description. This modification allows for more flexible node expansion control, enabling specific nodes to be expanded by their identifiers while providing a clear default state of an empty array.

Changes

File	Change Summary
examples/sites/demos/apis/tree.js	Updated default-expanded-keys property: - Type changed from boolean to string[] - Default value changed from false to [] - Enhanced description for property behavior

Possibly related PRs

• fix(tree): [tree] fix parent node toggle when click child node margin #2501: Addresses tree component node interaction, potentially related to node expansion behavior
• feat(tree-menu): [tree-menu] Resolve the warning issue on the tree-menu #2627: Introduces new properties to tree-menu component, which might interact with expanded keys
• feat(theme): optimize the overall basic variables and update treeMenu css var #2534: Modifies tree-menu component specification, potentially aligned with current changes

Suggested labels

bug

Suggested reviewers

• zzcr

Poem

🌳 A tree of keys, once simple and plain,
Now branching out with strings to gain,
Expanded nodes, a flexible sight,
From boolean's limits, taking flight!
🐰 Code grows wild, like branches free! 🌿

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.

---

📜 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 926fb6e and 8be3974.

📒 Files selected for processing (1)

• examples/sites/demos/apis/tree.js (1 hunks)

🔇 Additional comments (1)

examples/sites/demos/apis/tree.js (1)

135-140: LGTM! The property definition is now more accurate and clear.

The changes to default-expanded-keys property are well-structured and improve the API documentation by:

1. Correcting the type from boolean to string[] to accurately reflect its purpose
2. Setting an appropriate default value of []
3. Providing a clearer description of the dynamic behavior when the property changes

---

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?

❤️ 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. (Beta)
• @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]

[e2e-test-warn]
The component to be tested is missing.

The title of the Pull request should look like "fix(vue-renderless): [action-menu, alert] fix xxx bug".

Please make sure you've read our contributing guide