-
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
Fix typo in use-block-sync tests #67145
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. |
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.
Good spotting!
Amazingly the tests still work(ed)
It is worth adding a fail scenario to catch this in the future? Not a blocker, just asking...
Size Change: 0 B Total Size: 1.82 MB ℹ️ View Unchanged
|
Flaky tests detected in 69e3004. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/11927971803
|
I don't think there's an easy way to do that. This typo has also already caused me quite a lot of wasted time, so I'd be very happy to move on from it 😄 Thanks for the approval 👍 |
What?
Fixes a typo/bug in the
useBlockSync
unit tests.The typo causes
setHasControlledInnerBlocks
not to run for these tests, insteadreplaceInnerBlocks
is dispatched in place ofsetHasControlledInnerBlocks
with the args thatsetHasControlledInnerBlocks
would usually receive. This can cause some weird results, like theblocks
arg ofreplaceInnerBlocks
being a boolean value. 😵Amazingly the tests still work(ed) 🤨