docs: update example

[mynetfan]

• 跟进后端菜单逻辑的修改，现已无需传递basicLayout布局

fixed: #6034

Summary by CodeRabbit

• Documentation
  • Updated backend access control example by adding a "Test" menu entry that demonstrates a page without the default layout.
  • Improved clarity by removing a fixed comment and a hardcoded layout property from the menu example.

[changeset-bot]

⚠️ No Changeset found

Latest commit: a9d6979

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 documentation for backend access control menu data structure was updated. The fixed comment and the hardcoded component: 'BasicLayout' property were removed from the first menu item in the example. Additionally, a new "Test" menu entry was added, demonstrating a route that does not use the basic layout by specifying noBasicLayout: true in its metadata. These changes clarify that specifying BasicLayout is not required and provide an example of a special page layout.

Changes

File(s)	Change Summary
docs/src/guide/in-depth/access.md	Removed fixed comment and hardcoded BasicLayout from example menu; added "Test" menu entry with noBasicLayout: true.

Sequence Diagram(s)

sequenceDiagram
    participant Backend
    participant Frontend
    Backend->>Frontend: Return menu data (without BasicLayout)
    Frontend->>Frontend: Render menu
    alt Menu item with noBasicLayout: true
        Frontend->>Frontend: Render page without BasicLayout
    else
        Frontend->>Frontend: Render page with BasicLayout
    end

Loading

Assessment against linked issues

Objective	Addressed	Explanation
Remove requirement for BasicLayout in backend API menu example (#6034)	✅

Suggested reviewers

• anncwb
• jinmao88
• vince292007

Poem

A hop and a skip through docs we go,
No more layouts set in stone to show!
"Test" hops in, unique and bright,
Skipping the sidebar, feeling light.
With menus now clear as a springtime day,
This bunny cheers, "Hip hip hooray!" 🐇

---

📜 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 5ffd7db and a9d6979.

📒 Files selected for processing (1)

• docs/src/guide/in-depth/access.md (1 hunks)

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

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

🔇 Additional comments (1)

docs/src/guide/in-depth/access.md (1)

145-154: Approve addition of the "Test" route example with noBasicLayout

The new menu entry succinctly demonstrates how to exclude a page from the default layout. The Chinese comment explaining noBasicLayout: true is clear and consistent with the surrounding documentation.

---

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 generate sequence diagram to generate a sequence diagram of the changes in 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.