Docs: Add post meta limitations to Block Bindings API docs #68583
+3
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
t-hamano
added
[Type] Developer Documentation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.mdScreenshots or screencast