Releases: Automattic/vip-block-data-api
Releases · Automattic/vip-block-data-api
1.4.3
What's Changed
- Bump latest supported WordPress version to 6.7 by @alecgeatches in #84
Full Changelog: 1.4.2...1.4.3
1.4.2
What's Changed
- Fix raw attribute sources with multiple nodes in #82. Thank you @veerap000 for your report and suggested fix!
- Fix test failure related to block binding alias changes in WordPress by @chriszarate in #83
- Add minimum PHP and WordPress version notice by @ingeniumed in #80
Full Changelog: 1.4.1...1.4.2
1.4.1
What's Changed
- Fix #77, so that the plugin works again on PHP 8.0 and PHP 8.1
Full Changelog: 1.4.0...1.4.1
1.4.0
What's Changed
- Add block binding support by @chriszarate in #74.
- Add synced patterns (AKA reusable blocks) support by @chriszarate in #75
Both of these additions take advantage of new WordPress content features and ensure data is rendered correctly via the Block Data API. Thank you to @chriszarate for these contributions!
Full Changelog: 1.3.0...1.4.0
1.3.0
What's Changed
- #66: Fixes several data type representations in GraphQL output, including boolean and number values. Note that this only applies to the new
blocksDataV2
property and does not change existing behavior inblocksData
queries. - #72: Adds a
blocksDataV2
property to posts in GraphQL. Contains the above data type fixes, and also alters the block flattening format to be simpler. Check out the updated GraphQL and Block hierarchy reconstruction sections in the README. - #71: Fix
*
selectors used inanchor
andariaLabel
attributes. Also see this filter to register client-side attributes from block supports. - #70: Minor test addition to clarify how we represent missing attributes without defaults.
Thank you to @Zamfi99 for contributing code and discussion!