Skip to content

fix(gatsby-source-wordpress): restore PQR support #33590

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Oct 19, 2021
Merged

fix(gatsby-source-wordpress): restore PQR support #33590

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 8 additions & 5 deletions packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/index.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,12 +9,15 @@ import { buildNodeQueries } from "./build-queries-from-introspection/build-node-
import { cacheFetchedTypes } from "./cache-fetched-types"
import { writeQueriesToDisk } from "./write-queries-to-disk"

/**
* This fn is called during schema customization.
* It pulls in the remote WPGraphQL schema, caches it,
* then builds queries and stores a transformed object
* later used in schema customization.
*
* This fn must run in all PQR workers.
*/
const ingestRemoteSchema = async (helpers, pluginOptions) => {
// don't ingest schema while in worker - use cache instead
if (process.env.GATSBY_WORKER_POOL_WORKER) {
return
}

if (process.env.NODE_ENV === `development`) {
// running this code block in production is problematic for PQR
// since this fn will run once for each worker and we need the result in each
Expand Down