Releases: wpengine/wp-graphql-content-blocks
Releases · wpengine/wp-graphql-content-blocks
v4.0.0
Breaking Changes
-
ed23a32: BREAKING: Update Schema to reflect latest WordPress 6.5 changes.
- WHAT the breaking change is: Added new
rich-text
type - WHY the change was made: WordPress 6.5 replaced some of the attribute types from string to
rich-text
causing breaking changes to the existing block fields. - HOW a consumer should update their code: If users need to use WordPress >= 6.5 they need to update this plugin to the latest version and update their graphql schemas.
- WHAT the breaking change is: Added new
Patch Changes
- d62e8db: chore: remove
squizlabs/php_codesniffer
from Composer's direct dependencies. - e348494: fix: handle arrays before casting when using
Block::normalize_attribute_value()
- 7bf6bcb: fix: Change Block:get_block_attribute_fields()
$prefix parameter be an optional
string`. - e6b4ac4: chore: update Composer dev-deps and lint
- 05b21b5: fix: Update parameter type for
$supported_blocks_for_post_type_context
inwpgraphql_content_blocks_should_apply_post_type_editor_blocks_interfaces
to support boolean values - 7b49863: chore: Bump PHPStan.neon.dist to level 8 and generate baseline of existing tech debt.
- 0c8e2c7: fix: check for
post_content
before attempting to parse them. - 8eb1bb8: chore: remove unnecessary
isset()
in Anchor::get_block_interfaces(). - bdff4fb: dev: inline and remove
Block::resolve()
and makename
field nullable. - 9b0a63e: fix: Ensure valid
WP_Block_Type
before applyingAnchor
interfaces. - 2d4a218: fix: : rename
WPGraphQLHelpers
file to match class casing. The file name has been changed fromincludes/Utilities/WPGraphqlHelpers.php
toincludes/Utilities/WPGraphQLHelpers.php
. - d00ee4a: fix: rename
DomHelpers.php
toDOMHelpers.php
and improve type-safety of internal methods. - 66f74fb: chore: stub WP_Post_Type and boostrap wp-graphql-content-blocks.php when scanning with PHPStan
- ad03a21: fix: Don't register
NodeWithEditorBlocks
interface tonull
type names. - 43791db: chore: update PHPStan ruleset for stricter linting, and address newly-discovered tech debt.
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.