Skip to content
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

fix(gatsby-source-wordpress): prevent inconsistent schema customization #37749

Merged
merged 17 commits into from
Mar 16, 2023

Conversation

TylerBarnes
Copy link
Contributor

@TylerBarnes TylerBarnes commented Mar 16, 2023

Fixes #37729
Canary available as gatsby-source-wordpress@7.8.0-alpha-wp-inconsistent-schema.29

The problem here was source-wordpress was only excluding some problematic types on initial builds and then re-including them on cached builds. This wasn't a problem before but due to a change in WPGraphQL 1.14.0 this ended up producing an invalid schema which would fail builds.

In order to figure out what was going wrong I had to write some code that diffed the built schema customization types and outputted a warning. Since it was pretty useful I ended up keeping that warning in for gatsby develop so we can catch these kinds of problems in the future if they occur again for some other reason.

I also removed some types from snapshots because those types are newly excluded. I excluded them because they're just connection types to previously excluded types and I don't want them to cause problems in the future.

@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Mar 16, 2023
@TylerBarnes TylerBarnes added topic: source-wordpress Related to Gatsby's integration with WordPress and removed status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer labels Mar 16, 2023
kathmbeck
kathmbeck previously approved these changes Mar 16, 2023
@TylerBarnes TylerBarnes added the bot: merge on green Gatsbot will merge these PRs automatically when all tests passes label Mar 16, 2023
@TylerBarnes TylerBarnes merged commit 9f26b67 into master Mar 16, 2023
@TylerBarnes TylerBarnes deleted the fix/wp-inconsistent-schema-customization branch March 16, 2023 22:40
pieh pushed a commit that referenced this pull request Mar 23, 2023
…on (#37749)

* panic or warn when schema customization is inconsistent

* ensure types are always properly excluded

* add blocklist of typename parts which cause a type to be excluded if it's name includes a part

(cherry picked from commit 9f26b67)
pieh pushed a commit that referenced this pull request Mar 23, 2023
…on (#37749)

* panic or warn when schema customization is inconsistent

* ensure types are always properly excluded

* add blocklist of typename parts which cause a type to be excluded if it's name includes a part

(cherry picked from commit 9f26b67)
pieh added a commit that referenced this pull request Mar 30, 2023
…on (#37749) (#37778)

* fix(gatsby-source-wordpress): prevent inconsistent schema customization (#37749)

* panic or warn when schema customization is inconsistent

* ensure types are always properly excluded

* add blocklist of typename parts which cause a type to be excluded if it's name includes a part

(cherry picked from commit 9f26b67)

* ignore browserlist update prompt

* fix ignore

* fix(gatsby-source-wordpress): Force removal of types (#37424)

---------

Co-authored-by: Tyler Barnes <tylerdbarnes@gmail.com>
Co-authored-by: Michal Piechowiak <misiek.piechowiak@gmail.com>
Co-authored-by: Ty Hopp <tyhopp@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bot: merge on green Gatsbot will merge these PRs automatically when all tests passes topic: source-wordpress Related to Gatsby's integration with WordPress
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Gatsby-source-wordpress: ERROR #11321 after upgrading WPGraphQL to 1.14.0
2 participants