-
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 Bindings: Bootstrap server sources earlier #66058
base: trunk
Are you sure you want to change the base?
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. |
Size Change: -213 B (-0.01%) Total Size: 1.77 MB
ℹ️ View Unchanged
|
Tests are failing, it seems that now requires to not set a label here: gutenberg/packages/e2e-tests/plugins/block-bindings/index.js Lines 20 to 26 in fe88860
|
That makes sense. I just pushed a commit to change that. |
What?
Fixes #66031
In this pull request, I'm proposing removing the existing way of bootstrapping the sources defined in the server and do it directly in core with an inline script.
Why?
In the current implementation, bootstrapping happens in
initializeEditor
, which happens after dom ready. This means that when a external source is registered in the server and in the client, the bootstrap happens too late, causing unexpected behaviors.How?
I removed the existing logic and added a filter to add an inline script registering the server sources. This will be replicated in core.
Testing Instructions
e2e should pass.
The issue reported here should be fixed.