-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gatsby Schema Update Breaking Change #22
Comments
Hi would you be able to let me know what versions of the Yoast WpGraphQL plugin you are using? |
Version 4.2.0, thanks!
I also have the following plugins enabled:
Yoast v. 18.2
WP Gatsby v. 2.3.2
WP GraphQL v. 1.6.12
WP GraphQL for ACF v 0.5.3
…On Thu, Feb 24, 2022 at 5:28 AM Ashley Hitchcock ***@***.***> wrote:
With the latest version of the WpGraphQL I have not removed this so it
should still be there for Gatsby to source.
[image: image]
<https://user-images.githubusercontent.com/2438290/155506839-c91f422f-d761-4f55-b182-f549d693d582.png>
—
Reply to this email directly, view it on GitHub
<#22 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGXOVGL4MFKO27VEMQRY23U4YB5DANCNFSM5PFIKCJA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Gatsby specific Yoast WPGraphQL Schema seems to have updated several fields and is now breaking the GraphQL query, for instance the field contentTypes is no longer available. Seo is now embedded in each content type field (WpPost, WpPage, etc). As a result, the SEO parser is unable to map back to the proper schema and is resulting in breaking updates.
Please see the following issue with Gatsby GraphiQL
The text was updated successfully, but these errors were encountered: