-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Pattern Overrides: Refactor pattern (wp:block
) block to use the block binding editing API
#59817
Comments
Note here that the Having said that, I started this branch as an experiment to see how it could work. It's on my to-do list to review it and open an experimental PR at some point. |
@SantosGuillamot How much time do you think that will take? Hopefully it isn't something that will end up being merged very close to the 6.6 beta, I'd rather see these changes made early, and pattern overrides can even help inform the implementation. |
Editing the value of the sources, which is what is needed for this use case, it's planned to be the top priority of block bindings for 6.6: link. And to do that, the API must meet the requirements for pattern overrides. I can't say how much time it will take to be ready, but I feel confident that it will be available earlier in the release process. |
@SantosGuillamot Is there an update on the status of |
We've spent some time to understand better the different use cases and requirements for |
wp:block
) block to use the block binding useSource
functionwp:block
) block to use the block binding editing API
What problem does this address?
As mentioned in #53705 (comment), it'd be good to explore making the pattern block use the block bindings
useSource
API that was introduced in #58085.edit:
useSource
was replaced in Block bindings: don't use hooks, so this issue should now be about using that new block bindings editing API.The text was updated successfully, but these errors were encountered: