Skip to content

fix: created a block and reset the parent page#1312

Closed
1degrees wants to merge 2 commits into
opentiny:developfrom
1degrees:fix/createBlockBug
Closed

fix: created a block and reset the parent page#1312
1degrees wants to merge 2 commits into
opentiny:developfrom
1degrees:fix/createBlockBug

Conversation

@1degrees
Copy link
Copy Markdown
Contributor

@1degrees 1degrees commented Apr 15, 2025

English | 简体中文

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

What is the current behavior?

Issue Number: #1311

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Summary by CodeRabbit

  • Bug Fixes
    • Improved handling when importing schemas with a component named 'Block', ensuring proper page context resetting and updates.

@github-actions github-actions Bot added the bug Something isn't working label Apr 15, 2025
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 15, 2025

Walkthrough

The callback for the 'schemaImport' subscription in the RenderMain module was updated to introduce conditional logic. Now, when a schema is imported, the code retrieves the schema from window.host.getSchema(), checks if its componentName is constants.COMPONENT_NAME.Block, and if so, resets the pageContext.pageId and updates page ancestry before setting the schema. Previously, the schema was set directly without these additional steps.

Changes

File(s) Change Summary
packages/canvas/render/src/RenderMain.ts Modified the 'schemaImport' callback to add conditional logic for schemas with Block componentName, including resetting pageContext.pageId and updating ancestry before setting the schema. Added import of constants from @opentiny/tiny-engine-utils.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant RenderMain
    participant window.host
    participant pageContext

    User->>RenderMain: schemaImport event
    RenderMain->>window.host: getSchema()
    window.host-->>RenderMain: schema
    RenderMain->>RenderMain: Check schema.componentName == constants.COMPONENT_NAME.Block
    alt If componentName is 'Block'
        RenderMain->>pageContext: pageId = ""
        RenderMain->>RenderMain: updatePageAncestor()
    end
    RenderMain->>RenderMain: setSchema(schema)
Loading

Poem

A schema hops in, a 'Block' at the gate,
The pageId resets, we don't hesitate!
Ancestors updated, the context is clear,
With logic refined, the changes appear.
The code is now smarter, the flow is in tune—
A rabbit approves, and whistles a tune! 🐇


📜 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 0d341ef and be6c0db.

📒 Files selected for processing (1)
  • packages/canvas/render/src/RenderMain.ts (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • packages/canvas/render/src/RenderMain.ts
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: push-check
✨ Finishing Touches
  • 📝 Generate Docstrings

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

@hexqi hexqi added this to the v2.5.0 milestone Apr 16, 2025
callback: () => {
setSchema(window.host.getSchema())
const schema = window.host.getSchema()
if (schema.componentName === 'Block') {
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

建议使用定义的常量:

import { constants } from '@opentiny/tiny-engine-utils'
if (schema.componentName === constants.COMPONENT_NAME.Block) {
  // ...
}

Copy link
Copy Markdown
Collaborator

@gene9831 gene9831 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

查看 #1323 的解决方案,此修改方案没有修正url错误的问题

@hexqi hexqi removed this from the v2.5.0 milestone Apr 22, 2025
@1degrees 1degrees closed this Apr 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants