fix(docs): Fixed an issue where the opentiny/vue-docs package version 3.18 cannot use the meta tag.

[chenxi-20]

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

Release Notes

• New Features

  • Enhanced metadata representation for various components, indicating stable versions.
  • Improved clarity in API documentation for components like dropdown, pager, and grid.
  • Introduced new computed properties in the VersionTip component for better version stage handling.

• Bug Fixes

  • Streamlined error handling and logic flow in the components.

• Documentation

  • Updated descriptions and types in API documentation for consistency and clarity across components.

• Style

  • Adjusted styling for improved visual layout and responsiveness in the components.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes in this pull request involve updates to several API definitions across various components, including button-group, dialog-select, dropdown, grid, input, pager, and pop-upload. The primary modifications include renaming the metaData field to meta and updating versioning information from new to stable. Additionally, there are clarifications in type definitions and descriptions for properties across these components. The overall structure of the APIs remains intact, with a focus on enhancing clarity and consistency in metadata representation.

Changes

File Path	Change Summary
examples/sites/demos/apis/button-group.js	- metaData in empty slot changed to meta, updated from new: '3.17.0' to stable: '3.17.0' - IButtonGroupData interface value type changed to `number
examples/sites/demos/apis/dialog-select.js	- footer-buttons slot metaData changed to meta, updated from new: '3.18.0' to stable: '3.18.0'
examples/sites/demos/apis/dropdown.js	- metaData changed to meta - Property types updated from Boolean to boolean for border, round, single-button, visible-arrow - Updated types for menu-options, trigger, size, custom-class, level, max-height, and options
examples/sites/demos/apis/grid.js	- custom-column-names and toggle-group-change metadata changed from metaData with new to meta with stable
examples/sites/demos/apis/input.js	- show-tooltip property metaData changed to meta, updated from new: '3.18.0' to stable: '3.18.0'
examples/sites/demos/apis/pager.js	- total-fixed-left metadata changed from metaData to meta, updated to stable - Updated descriptions for properties for clarity, changed page-size type from Number to number
examples/sites/demos/apis/pop-upload.js	- uploadTip slot metaData changed to meta, updated from new: '3.18.0' to stable: '3.18.0'
examples/sites/package.json	- Version updated from 3.18.5 to 3.18.6
examples/sites/src/views/components/VersionTip.vue	- Updated STAGE enum, removed removed and new, added toBeRemoved - Renamed metaData prop to meta - Added isFromMenu prop with default false
examples/sites/src/views/components/components.vue	- Updated version-tip component prop from metaData to meta - Added new variables and methods for improved component functionality and loading logic

Possibly related PRs

• refactor(dropdown-menu): [dropdown] refactor DropdownMenu and DropdownItem vars and style #2208: Refactor of DropdownMenu and DropdownItem components may relate to the changes in the button-group API, as both involve UI components and their configurations.
• refactor(grid): [grid] refactor grid style #2241: Refactor of grid styles could be relevant due to potential shared styling or structural changes that might affect button-group components.
• docs: fix demo anchor position not correct #2391: Fixing demo anchor positions may relate to the button-group if it involves navigation or interaction elements that include buttons.
• refactor(theme-doc): add ThemeTools docs #2403: Adding documentation for ThemeTools could be relevant as it may affect how button-group components are styled or configured within themes.
• docs(auto-tip): [directives] updateauto-tip and highlight-query docs and demos #2406: Updates to auto-tip and highlight-query documentation may relate to button-group interactions if tooltips are used in conjunction with buttons.
• fix(docs): Fixed an issue with the loading level of the document. #2411: Fixing loading levels in documentation could indirectly relate to button-group if it affects how buttons are displayed or interacted with in the documentation.
• fix(theme): remove oldTheme's DOCS #2417: Removing oldTheme's documentation may relate to button-group if it affects legacy styling or configurations that include buttons.
• fix(tabs): [tabs] Fixed the floating issue of the close button on the tab page and the style issue of the close button under the buttoncard. #2425: Fixing styling issues with tabs could be relevant if button-group components are used in conjunction with tabbed interfaces.
• feat: add changelog and remove rich-text-editor menu #2448: Adding a changelog and removing the rich-text-editor menu may relate to the overall UI structure that includes buttons.
• fix(steps): repair bar step bar small gray dots #2459: Fixing styling issues with the steps component may relate to button-group if they share similar styling or layout concerns.
• fix(tag): remove mini size of tag #2468: Removing the mini size of the tag directly relates to button-group as it may affect how tags are displayed alongside buttons in the UI.

Suggested labels

bug

Suggested reviewers

• zzcr

🐇 In the meadow, changes abound,
With buttons and dropdowns, clarity found.
Metadata shifts from new to stable,
Enhancing our code, as best we are able!
So hop with joy, let the updates ring,
For a better API, let the rabbits sing! 🐇

---

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 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