티스토리 수익 글 보기
{{ message }}
Block Bindings in WordPress 7.0 #73467
Description
Supersedes #67520.
Enhancements
- Filter available source items for a given attribute by format.
- See this preliminary exploration and discussion.
- We’ll do this in close collaboration with @oandregal, who’s approaching formats for the Fields API. See the tracking issue and this example.
- Open up “Pattern Overrides” and therefore intern block bindings to custom dynamic blocks #64870
Explorations
- Bind multiple attributes to a single source. Example: Bind Image block’s
url,alt,titleattributes to post’s featured image (exposed viacore/post-datasource).- Related exploration: Block Bindings: Try using
__defaultfor generic bindings #71002
- Related exploration: Block Bindings: Try using
- Try binding a block that requires a “repeater” concept. Example: Bind Gallery block to list of images.
- Streamline the API based on recurring usage patterns in
getValuesandgetFieldsList.- Examples include passing more arguments to them (e.g. block name, attributes); or providing additional ways for a block source to communicate that it will not expose and source items for a given block, attribute, or other context. (Things that are currently done by e.g. returning
[]fromgetFieldsList, based on certain criteria.)
- Examples include passing more arguments to them (e.g. block name, attributes); or providing additional ways for a block source to communicate that it will not expose and source items for a given block, attribute, or other context. (Things that are currently done by e.g. returning
- Block Bindings: Add support for the block
visibilityattribute #73461 - Remove requirement to define a block bindings source both on the server and client side. Instead, allow server-side only definition, and communicate to the client. See this comment, bullet point 4, for a suggestion how to do this.
- contentOnly pattern experiment: add inspector ‘fields’ support for Pattern Overrides and Block Bindings #73423