-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Block Editor: insertDefaultBlock
should not trigger an error if the default block is not registered
#38886
Conversation
Size Change: +12 B (0%) Total Size: 1.15 MB
ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense. Apparently yield undefined
used to work and was noop, as because it wasn't detected as action object it was never dispatched to Redux. But now it was dispatched and Redux doesn't like undefined
actions 👍
Thanks for catching this.
Thanks for the review, @jsnajdr. |
insertDefaultBlock
should not trigger an error if the default block is not registered
Description
When the default block isn't registered the
insertDefaultBlock
triggers the following Redux error:Testing Instructions
Running this e2e test shouldn't print the error above -
npm run test-e2e -- packages/e2e-tests/specs/editor/various/block-deletion.test.js
wp.data.dispatch('core/blocks').removeBlockTypes('core/paragraph');
Screenshots
Types of changes
Checklist:
*.native.js
files for terms that need renaming or removal).