-
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
Make use of accessing private APIs from thunks directly #52214
Conversation
Size Change: +26 B (0%) Total Size: 1.43 MB
ℹ️ View Unchanged
|
Flaky tests detected in e9eddaa. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/5505756637
|
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.
This looks good to me.
ddedead
to
13bc185
Compare
weird these e2e test failures, are they related? |
They refuse to go away, even after rebase, after restarting... They might have a point, I'll investigate that. |
13bc185
to
e9eddaa
Compare
It turns out that I forgot to actually register the |
Since #51051, private selectors and actions are exposed to thunks directly, already unlocked. There are several opportunities in the Gutenberg codebase to use this new feature. This PR does that:
ensureDefaultBlock
, and accessingundoEdits
andredoEdits
.