Bot releases are hidden (Show)
Published by jasonbahl about 2 years ago
AbstractConnectionResolver::$args
handling by @justlevine in https://github.com/wp-graphql/wp-graphql/pull/2521
ID
inputs by @justlevine in https://github.com/wp-graphql/wp-graphql/pull/2522
Full Changelog: https://github.com/wp-graphql/wp-graphql/compare/v1.10.0...v1.11.0
Published by jasonbahl about 2 years ago
PR (#2490) fixes a bug that some users were using as a feature.
When a page is marked as the "Posts Page" WordPress does not resolve that page by URI, and this bugfix no longer will resolve that page by URI.
Here, you can read more about why this change was made and find a snippet of code that will bring the old functionality back if you've built features around it.
idType
arg to RootQuery.comment
. Thanks @justlevine!resetUserPassword
mutation. Thanks @justlevine!include
and exclude
args to MediaDetails.sizes
. Thanks @justlevine!mediaItems
query by mimeType
. Thanks @justlevine!databaseId
. Thanks @justlevine!Full Changelog: https://github.com/wp-graphql/wp-graphql/compare/v1.9.1...v1.10.0
Published by jasonbahl about 2 years ago
Full Changelog: https://github.com/wp-graphql/wp-graphql/compare/v1.9.0...v1.9.1
Published by jasonbahl about 2 years ago
There are 2 changes that might require action when updating to 1.9.0
When querying for a nodeByUri
, if your site has the "page_for_posts" setting configured, the behavior of the nodeByUri
query for that uri might be different for you.
Previously a bug caused this query to return a "Page" type, when it should have returned a "ContentType" Type.
The bug fix might change your application if you were using the bug as a feature.
There were a lot of bug fixes related to connections to ensure they behave as intended. If you were querying lists of data, in some cases the data might be returned in a different order than it was before.
For example, using the "last" input on a Comment or User query should still return the same nodes, but in a different order than before.
This might cause behavior you don't want in your application because you had coded around the bug. This change was needed to support proper backward pagination.
Comment.author
connections not properly resolving for public (non-authenticated) requests.If you were affected by #2464, here's a snippet that can help bring back previous behavior:
add_filter( 'graphql_pre_resolve_uri', function( $null, $uri, $context, $wp ) {
$page_for_posts = get_option( 'page_for_posts', 0 );
if ( empty( $page_for_posts ) ) {
return $null;
}
$permalink = get_permalink( (int) $page_for_posts );
if ( empty( $permalink ) || is_wp_error( $permalink ) ) {
return $null;
}
$parsed_permalink = wp_parse_url( $permalink );
$parsed_uri = wp_parse_url( $uri );
if ( ! isset( $parsed_permalink['path'] ) || ! isset( $parsed_uri['path'] )) {
return $null;
}
$trimmed_uri_path = rtrim( ltrim( $parsed_uri['path'], '/' ), '/' );
$trimmed_permalink_path = rtrim( ltrim( $parsed_permalink['path'], '/' ), '/' );
if ( $trimmed_permalink_path === $trimmed_uri_path ) {
return new \WPGraphQL\Model\Post( get_post( (int) $page_for_posts ) );
}
return $null;
}, 10, 4 );
You can read more about this here: https://github.com/wp-graphql/wp-graphql/issues/2486#issuecomment-1232169375
Published by jasonbahl about 2 years ago
contentNodes
field not showing if a taxonomy is registered without connected post types. Thanks @saimonh3!query_id
to after_execute_actions
for batch requests. Thanks @markkelnar!Full Changelog: https://github.com/wp-graphql/wp-graphql/compare/v1.8.6...v1.8.7
Published by jasonbahl over 2 years ago
Published by jasonbahl over 2 years ago
uri
to MenuItem by @josephfusco in https://github.com/wp-graphql/wp-graphql/pull/2363
Full Changelog: https://github.com/wp-graphql/wp-graphql/compare/v1.8.1...v1.8.2
Published by jasonbahl over 2 years ago
WPGraphQL::get_allowed_{type}( 'objects ')
by @justlevine in https://github.com/wp-graphql/wp-graphql/pull/2356
Full Changelog: https://github.com/wp-graphql/wp-graphql/compare/v1.8.0...v1.8.1
Published by jasonbahl over 2 years ago
menus
should return empty when location
doesn't have a menu assigned. by @justlevine in https://github.com/wp-graphql/wp-graphql/pull/2295
allow-plugins
to composer.json config by @justlevine in https://github.com/wp-graphql/wp-graphql/pull/2291
Utils::get_database_id_from_id()
for DRY handling of ID
types. by @justlevine in https://github.com/wp-graphql/wp-graphql/pull/2322
before
or after
are empty. by @justlevine in https://github.com/wp-graphql/wp-graphql/pull/2293
commentType
by @justlevine in https://github.com/wp-graphql/wp-graphql/pull/2320
update
to activate
by @justlevine in https://github.com/wp-graphql/wp-graphql/pull/2327
WP_Comment
object to comment_text
filter by @justlevine in https://github.com/wp-graphql/wp-graphql/pull/2319
Full Changelog: https://github.com/wp-graphql/wp-graphql/compare/v1.7.2...v1.8.0
Published by jasonbahl over 2 years ago
Full Changelog: https://github.com/wp-graphql/wp-graphql/compare/v1.7.1...v1.7.2
Published by jasonbahl over 2 years ago
This release includes a re-write of the WPGraphiQL IDE.
Not only is the UI updated, but the codebase has been re-written completely to allow for 3rd party plugins to hook/filter the functionality and extend it.
You can now write GraphiQL extensions that interact with the GraphiQL IDE, and have access to the same React Context / State as the rest of the app.
This sets the stage for tools like WPGraphQL for WooCommerce, WPGraphQL for ACF and Atlas Content Modeler to provide custom tools that enhance their users experience of using the GraphiQL IDE.
In addition to the updated UI and extension-friendly architecture, WPGraphiQL now includes one of the most requested features for the tool: a button that lets you toggle between executing requests as a public (non-authenticated) user and an authenticated user (who you're logged in to the WordPress dashboard as).
updateUser
mutation. Thanks @victormattosvm!pageByUri
query might return incorrect data when custom permalinks are set. Thanks @blakewilson!register_setting()
API would cause Schema Introspection failures, causing GraphiQL and other tools to not work properly.avatar
for the CommentAuthor Type and the Commenter Interface type.graphql_model_prepare_fields
filter and deprecates graphql_return_modeled_data
filter. Thanks @justlevine!Published by jasonbahl over 2 years ago
Full Changelog: https://github.com/wp-graphql/wp-graphql/compare/v1.6.11...v1.6.12
Published by jasonbahl almost 3 years ago
prepare_fields()
statically by @justlevine in https://github.com/wp-graphql/wp-graphql/pull/2197
Full Changelog: https://github.com/wp-graphql/wp-graphql/compare/v1.6.10...1.6.11
Published by jasonbahl almost 3 years ago
Published by jasonbahl almost 3 years ago
Published by jasonbahl almost 3 years ago
graphql_wp_connection_type_config
filter. by @justlevine in https://github.com/wp-graphql/wp-graphql/pull/2141
taxonomyName
field by @jeanfredrik in https://github.com/wp-graphql/wp-graphql/pull/2143
Full Changelog: https://github.com/wp-graphql/wp-graphql/compare/v1.6.7...v1.6.8