Releases: wpengine/wp-graphql-content-blocks
Releases · wpengine/wp-graphql-content-blocks
v3.1.2
v3.1.1
v3.1.0
v3.0.0
Major Changes
-
f15f95c: Adds missing default value for content attribute CoreParagraph and CoreCode blocks. This will make the type of the content field
String!
instead ofString
-
9b71411: Feature: Add support for querying array type query data from blocks
Query source block attribute types are supported. See: https://developer.wordpress.org/block-editor/reference-guides/block-api/block-attributes/#query-source
Patch Changes
- be7a34f: Interface Types are now registered with the Post Type's
graphql_single_name
, instead of the Post Type'sname
. Fixes a bug where invalid Types were registered.
v2.0.0
Major Changes
- 7251fb0: Fix: use
use_block_editor_for_post_type
instead ofpost_type_supports
when filtering the post types.
BREAKING: Potential schema changes for GraphQL Types representing a Post Type that does not use the Block Editor. Each GraphQL Type representing a Post Type that does not have block editor support previously would have had theeditorBlocks
field but that field will no longer exist on those Types.
v1.2.1
v1.2.0
Minor Changes
- a118662: Added new
wpgraphql_content_blocks_should_apply_post_type_editor_blocks_interfaces
filter to allow controlling whether ${PostType}EditorBlock interfaces should be applied.
Patch Changes
-
2e7f2e8: Refactored
register_block_types
to remove usages ofregister_graphql_interfaces_to_types
to improve performance.Deprecated
Anchor::register_to_block
public static method.