-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Make getLastInsertedBlocksClientIds selector private #47638
Make getLastInsertedBlocksClientIds selector private #47638
Conversation
Size Change: +11 B (0%) Total Size: 1.31 MB
ℹ️ View Unchanged
|
Flaky tests detected in 25c2365. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/4062863673
|
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.
LGTM, thanks!
* Make selector private and update docs * Unlock selector at point of usage
I just cherry-picked this PR to the release/15.1 branch to get it included in the next release: 8a907ca |
What?
Makes the
getLastInsertedBlocksClientIds
selector introduced in #46531 a private selector.Why?
In preparation for WP 6.2 we need to audit APIs that should be experimental.
In #46531 I introduced a new selector. This should probably be experimental as it's very new and unproven and the API may still be in flux as evidenced by the changes required to it since it was originally added.
How?
Use the new
lock
/unlock
API to make an experimental selector following the pattern already in place within the block editor package.Testing Instructions
Check tests pass