fix: preview ancestor has folder will get plain page

[chilingling]

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)
• Built its own designer, fully self-validated

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:

Background and solution

【问题描述】
使用 url 预览页面时（即非实时预览模式），如果祖先页面有文件夹，则会预览得到空页面。

【问题分析】
如果有文件夹的时候，文件夹出码得到的是空 div。

【问题修复方案】
获取祖先页面的时候，过滤文件夹。

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

  • Improved page hierarchy display by ensuring only actual pages are shown as ancestors.

• Bug Fixes

  • Ancestor lists now exclude non-page items for more accurate navigation and context.

[coderabbitai]

Warning

Rate limit exceeded

@chilingling has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 20 minutes and 57 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between d364c9b and e423842.

📒 Files selected for processing (55)

• designer-demo/package.json (1 hunks)
• mockServer/package.json (1 hunks)
• packages/block-compiler/package.json (1 hunks)
• packages/blockToWebComponentTemplate/package.json (1 hunks)
• packages/build/vite-config/package.json (1 hunks)
• packages/build/vite-plugin-meta-comments/package.json (1 hunks)
• packages/builtinComponent/package.json (1 hunks)
• packages/canvas/package.json (1 hunks)
• packages/common/package.json (1 hunks)
• packages/configurator/package.json (1 hunks)
• packages/design-core/package.json (1 hunks)
• packages/engine-cli/package.json (1 hunks)
• packages/engine-cli/template/designer/package.json (2 hunks)
• packages/i18n/package.json (1 hunks)
• packages/layout/package.json (1 hunks)
• packages/plugins/block/package.json (1 hunks)
• packages/plugins/bridge/package.json (1 hunks)
• packages/plugins/datasource/package.json (1 hunks)
• packages/plugins/help/package.json (1 hunks)
• packages/plugins/i18n/package.json (1 hunks)
• packages/plugins/materials/package.json (1 hunks)
• packages/plugins/page/package.json (1 hunks)
• packages/plugins/robot/package.json (1 hunks)
• packages/plugins/schema/package.json (1 hunks)
• packages/plugins/script/package.json (1 hunks)
• packages/plugins/state/package.json (1 hunks)
• packages/plugins/tree/package.json (1 hunks)
• packages/plugins/tutorial/package.json (1 hunks)
• packages/register/package.json (1 hunks)
• packages/settings/design/package.json (1 hunks)
• packages/settings/events/package.json (1 hunks)
• packages/settings/panel/package.json (1 hunks)
• packages/settings/props/package.json (1 hunks)
• packages/settings/styles/package.json (1 hunks)
• packages/svgs/package.json (1 hunks)
• packages/theme/base/package.json (1 hunks)
• packages/toolbars/breadcrumb/package.json (1 hunks)
• packages/toolbars/clean/package.json (1 hunks)
• packages/toolbars/collaboration/package.json (1 hunks)
• packages/toolbars/fullscreen/package.json (1 hunks)
• packages/toolbars/generate-code/package.json (1 hunks)
• packages/toolbars/lang/package.json (1 hunks)
• packages/toolbars/lock/package.json (1 hunks)
• packages/toolbars/logo/package.json (1 hunks)
• packages/toolbars/media/package.json (1 hunks)
• packages/toolbars/preview/package.json (1 hunks)
• packages/toolbars/redoundo/package.json (1 hunks)
• packages/toolbars/refresh/package.json (1 hunks)
• packages/toolbars/save/package.json (1 hunks)
• packages/toolbars/setting/package.json (1 hunks)
• packages/toolbars/themeSwitch/package.json (1 hunks)
• packages/toolbars/view-setting/package.json (1 hunks)
• packages/utils/package.json (1 hunks)
• packages/vue-generator/package.json (1 hunks)
• packages/webcomponent/package.json (1 hunks)

Walkthrough

The IPage interface was updated to include a new boolean property, isPage. In the getPageOrBlockByApi function, the logic for retrieving ancestor pages now filters the ancestors list to include only items where isPage is true, ensuring only actual pages are considered.

Changes

Cohort / File(s)	Change Summary
Page Interface and Ancestor Filtering packages/design-core/src/preview/src/preview/usePreviewData.ts	Added isPage: boolean to IPage interface; updated ancestor retrieval to filter by isPage.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

A bunny hops through code so bright,
Adding isPage to set things right.
Ancestors filtered, only pages remain,
Cleaner logic, less to explain.
With every hop and every tweak,
The code grows stronger, week by week! 🐇✨

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate unit tests to generate unit tests for 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.