Docs: Add post meta limitations to Block Bindings API docs #68583
Conversation
694f450 to
eb44ac7
Compare
|
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.
Thank you, @himanshupathak95!
Maybe we should move the callout below the meta registration example in this section: https://developer.wordpress.org/block-editor/reference-guides/block-api/block-bindings/#server-registration.
What do you think?
I think that would make much more sense and look better. Thanks for the suggestion :) |
d13d681 to
2f88a13
Compare
|
Failing tests are unrelated; I will look into it. |
…#68583) Co-authored-by: himanshupathak95 <abcd95@git.wordpress.org> Co-authored-by: Mamaduka <mamaduka@git.wordpress.org> Co-authored-by: andreawetzel <awetz583@git.wordpress.org>
Closes: #68574
What?
Add documentation about post-meta limitations in the Block Bindings API documentation, specifically covering protected meta and REST API requirements.
Why?
The current Block Bindings documentation doesn't mention important limitations regarding post-meta usage. Developers need to know upfront that:
How?
Add a callout alert section in
docs/reference-guides/block-api/block-bindings.mdbefore the "Compatible blocks and their attributes" section. The callout follows the existing documentation style and alerts about both limitations clearly.Testing Instructions
/docs/reference-guides/block-api/block-bindings.md