-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Pattern: Don't render block controls when an entity is missing #65028
Conversation
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
@@ -254,7 +255,9 @@ function ReusableBlockEdit( { | |||
value: innerBlocks.length > 0 ? innerBlocks : blocks, | |||
onInput: NOOP, | |||
onChange: NOOP, | |||
renderAppender: blocks?.length ? undefined : blocks.ButtonBlockAppender, |
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.
An incorrect search-replace from #60721.
Size Change: +3 B (0%) Total Size: 1.78 MB
ℹ️ View Unchanged
|
I'm going to merge this; it's a minor fix. |
Thanks for the fix @Mamaduka 🙌 |
What?
PR updates the condition for rendering the
ReusableBlockControl
component.Why?
A missing entity can't be edited or reset its content to the source. This also prevents an unnecessary
OPTIONS
request.Testing Instructions
<!-- wp:block {"ref":1000000} /-->
.OPTIONS
request wasn't made for thewp/v2/blocks
endpoint.Testing Instructions for Keyboard
Same.