-
Notifications
You must be signed in to change notification settings - Fork 354
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: chore bug fix for v2.1 #953
Conversation
1. 修复清空画布报错的 bug 2. 修复区块加载错误的 bug 3. 修复画布拖拽组件到最前面的时候,组件会消失的 bug
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. 🗂️ Base branches to auto review (2)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
1. 修复清空画布报错的 bug 2. 修复区块加载错误的 bug 3. 修复画布拖拽组件到最前面的时候,组件会消失的 bug
English | 简体中文
PR
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
Background and solution
修复清空画布报错的 bug
【问题分析】
#916 PR 中,从
Modal.confirm
改成了useModal.confirm
,需要将异步改成exec
回调。【解决方案】
将
.then
报错改成exec
回调修复区块加载错误的 bug
【问题分析】
画布通信PR将
resState
改成了appSchemaState
,需要同步适配【解决方案】
将
resState
改成appSchemaState
修复画布拖拽组件到最前面的时候,组件会消失的 bug
【问题分析】
insert 操作,没有兼容
before
位置的场景。【解决方案】
insert 操作,兼容
before
位置的场景。使用 unshift 插入到 children 数组最前面What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information