-
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
Block Locking: Fix regression in selectors #51541
Conversation
Size Change: +5 B (0%) Total Size: 1.4 MB
ℹ️ View Unchanged
|
Flaky tests detected in 8bad90c. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/5279824324
|
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.
Logic makes sense 👍 thanks for adding tests!
* Block Locking: Fix regression in selectors * A minor adjustments to the e2e tests * Add e2e tests for block locking and template lock
What?
Regression was introduced in #51148.
PR fixes a regression when blocks were not able to override the
templateLock
via Block Locking API.Why?
Block locking should supersede template locking. See https://make.wordpress.org/core/2022/01/08/locking-blocks-in-wordpress-5-9/.
How?
When the
attributes.lock
value isn'tundefined
return early.Testing Instructions
I added e2e test coverage to catch regressions early. See 8bad90c.
Snippet