fix(site): fix site api table style

[zzcr]

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

  • Enhanced layout and organization of the API documentation display for improved user experience.

• Bug Fixes

  • Streamlined rendering conditions for API documentation elements to ensure accurate display.

• Style

  • Updated styles for better visual separation and responsiveness of API tables.

[coderabbitai]

Walkthrough

The pull request includes updates to the package.json file for the @opentiny/vue-docs project, changing the version from 3.19.4 to 3.19.7. Additionally, modifications were made to the components.vue file, where the template structure was reorganized to enhance the layout and presentation of API documentation. A new wrapper <div class="api-table-box"> was added to improve visual separation, and several rendering conditions were streamlined for better clarity, while maintaining existing functionality.

Changes

File Path	Change Summary
examples/sites/package.json	Updated version from 3.19.4 to 3.19.7. No changes to scripts or dependencies.
examples/sites/src/views/components/components.vue	Restructured template with a new wrapper <div class="api-table-box">, streamlined rendering logic, and minor CSS adjustments for improved layout and responsiveness.

Possibly related PRs

• fix(site): add <code> style in api-table #2139: This PR modifies the components.vue file, enhancing the rendering of the "desc" field within the tiny-grid-column component, which is relevant to the changes made in the main PR that also involves components.vue.
• fix(site): fix scroll bugs #2506: This PR addresses scrolling functionality in components.vue, which relates to the adjustments made in the main PR regarding the layout and organization of the API documentation display in the same file.

Suggested labels

bug

Poem

In the garden of code, where rabbits play,
A version was changed, in a bright new way.
With boxes and grids, the layout refined,
API docs clearer, for all to find.
Hop along, dear friends, let’s celebrate,
These changes in code, oh, how great! 🐇✨

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

examples/sites/src/views/components/components.vue (1)

871-880: Consider enhancing mobile responsiveness.

While the current styles fix the table layout issues, consider adding responsive breakpoints for better mobile support:

 .api-table-box {
   border-left: 1px solid rgb(239, 239, 245);
   border-right: 1px solid rgb(239, 239, 245);
   overflow-x: auto;
   width: 100%;
+  @media (max-width: 767px) {
+    margin: 0 -16px;  /* Negative margin to allow full-width scrolling */
+    width: calc(100% + 32px);
+  }
 }

 .api-table {
   width: 100%;
   min-width: 640px;
   table-layout: fixed;
   border-collapse: collapse;
 }

This enhancement will:

1. Allow the table to scroll horizontally on mobile devices
2. Prevent content from being cut off at the edges

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 4c65284 and 10579bd.

📒 Files selected for processing (2)

• examples/sites/package.json (1 hunks)
• examples/sites/src/views/components/components.vue (6 hunks)

✅ Files skipped from review due to trivial changes (1)

• examples/sites/package.json

🔇 Additional comments (2)

examples/sites/src/views/components/components.vue (2)

39-94: LGTM: Improved API table structure with consistent wrapper.

The addition of the api-table-box wrapper provides better visual containment and overflow handling for the API tables.

---

161-229: LGTM: Consistent API table structure maintained.

The wrapper implementation is consistently applied across different sections, maintaining a uniform layout structure.