Bot releases are visible (Hide)
Published by jasonbahl over 1 year ago
shouldShowAdminToolbar
field to the User type, resolving from the "show_admin_bar_front" meta value. Thanks @blakewilson!Published by jasonbahl over 1 year ago
deregister_graphql_mutation()
and graphql_excluded_mutations
filter. Thanks @justlevine!deregister_graphql_connection
and graphql_excluded_connections
filter. Thanks @justlevine!pageInfo
field to the Connection type.Published by jasonbahl almost 2 years ago
Full Changelog: https://github.com/wp-graphql/wp-graphql/compare/v1.13.6...v1.13.7
Published by jasonbahl almost 2 years ago
includeDefaultInterfaces
to connection config, allowing connections to be registered without the default Connection
and Edge
interfaces applied.. Thanks @justlevine!Full Changelog: https://github.com/wp-graphql/wp-graphql/compare/v1.13.5...v1.13.6
Published by jasonbahl almost 2 years ago
Full Changelog: https://github.com/wp-graphql/wp-graphql/compare/v1.13.4...v1.13.5
Published by jasonbahl almost 2 years ago
NOTE: (#2627) was supposed to have been released in 1.13.2, and is listed in the changelog for that version, but I botched that release and only released the changelog without the actual changes 🤦🏻♂️
Full Changelog: https://github.com/wp-graphql/wp-graphql/compare/v1.13.3...v1.13.4
Published by jasonbahl almost 2 years ago
update versions for WordPress.org deploys
Full Changelog: https://github.com/wp-graphql/wp-graphql/compare/v1.13.2...v1.13.3
Published by jasonbahl almost 2 years ago
Full Changelog: https://github.com/wp-graphql/wp-graphql/compare/v1.13.0...v1.13.1
Published by jasonbahl almost 2 years ago
The work to introduce the Connection
and Edge
(and other) Interfaces required the User.revisions
and RootQuery.revisions
connection to
change from resolving to the ContentRevisionUnion
type and instead resolve to the ContentNode
type.
We believe that it's highly likely that most users will not be impacted by this change.
Any queries that directly reference the following types:
...on UserToContentRevisionUnionConnection
...on RootQueryToContentRevisionUnionConnection
Would need to be updated to reference these types instead:
...on UserToRevisionsConnection
...on RootQueryToRevisionsConnection
For example:
{
viewer {
revisions {
... on UserToContentRevisionUnionConnection {
nodes {
__typename
... on Post {
id
uri
isRevision
}
... on Page {
id
uri
isRevision
}
}
}
}
}
revisions {
... on RootQueryToContentRevisionUnionConnection {
nodes {
__typename
... on Post {
id
uri
isRevision
}
... on Page {
id
uri
isRevision
}
}
}
}
}
{
viewer {
revisions {
... on UserToRevisionsConnection {
nodes {
__typename
... on Post {
id
uri
isRevision
}
... on Page {
id
uri
isRevision
}
}
}
}
}
revisions {
... on RootQueryToRevisionsConnection {
nodes {
__typename
... on Post {
id
uri
isRevision
}
... on Page {
id
uri
isRevision
}
}
}
}
}
WPMutationType
. Thanks @justlevine!deregister_graphql_type()
access function and corresponding graphql_excluded_types
filter. Thanks @justlevine!register_graphql_edge_fields()
and register_graphql_connection_where_args()
access functions. Thanks @justlevine!previews
field for non-publicly queryable post types, and limit the Previewable
Interface to publicly queryable post types.Comment.approved
field in favor of Comment.status: CommentStatusEnum
. Thanks @justlevine!NodeResolver::resolve_uri()
to its own method. Thanks @justlevine!Full Changelog
https://github.com/wp-graphql/wp-graphql/compare/v1.12.3...v1.13.0
Published by jasonbahl almost 2 years ago
Published by jasonbahl almost 2 years ago
Full Changelog: https://github.com/wp-graphql/wp-graphql/compare/v1.12.1...v1.12.2
Published by jasonbahl almost 2 years ago
Full Changelog: https://github.com/wp-graphql/wp-graphql/compare/v1.12.0...v1.12.1
Published by jasonbahl about 2 years ago
This release removes the ContentNode
and DatabaseIdentifier
interfaces from the NodeWithFeaturedImage
Interface.
This is considered a breaking change for client applications using a ...on NodeWithFeaturedImage
fragment that reference fields applied by those interfaces. If you have client applications doing this (or are unsure if you do) you can use the following filter to bring back the previous behavior:
add_filter( 'graphql_wp_interface_type_config', function( $config ) {
if ( $config['name'] === 'NodeWithFeaturedImage' ) {
$config['interfaces'][] = 'ContentNode';
$config['interfaces'][] = 'DatabaseIdentifier';
}
return $config;
}, 10, 1 );
WPGraphQL simplifies adding Custom Post Types and Taxonomies to the WPGraphQL Schema.
In this release, there are new options that allow for greater customization into how Post Types and Taxonomies interact with the WPGraphQL Schema.
We've written 2 blog posts about this:
Full Changelog: https://github.com/wp-graphql/wp-graphql/compare/v1.11.3...v1.12.0
Published by jasonbahl about 2 years ago
X-GraphQL-Keys
header output. Truncate keys based on a filterable max length. Output the skipped keys in extensions payload for debugging, and add skipped:$type
keys to the X-GraphQL-Keys header for nodes that are skipped.Published by jasonbahl about 2 years ago
Published by jasonbahl about 2 years ago
Full Changelog: https://github.com/wp-graphql/wp-graphql/compare/v1.11.0...v1.11.1