Skip to content

chore(gatsby-source-wordpress): remove runApisInSteps and call runApiSteps for each gatsby-node api - #37039

Merged
TylerBarnes merged 1 commit into
masterfrom
chore/wp-switch-to-individual-exports-gatsby-node
Nov 14, 2022
Merged

TylerBarnes merged 1 commit into
masterfrom
chore/wp-switch-to-individual-exports-gatsby-node

Conversation

@TylerBarnes

Copy link
Copy Markdown
Contributor

This will allow us to remove extra exports in DSG

@gatsbot gatsbot Bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Nov 14, 2022
@TylerBarnes

Copy link
Copy Markdown
Contributor Author

I ran the source-wordpress integration tests locally and all of them passed. I can't get the unrelated failing tests here to pass and those block the source-wordpress tests from passing here so I'm going to force merge this.

@TylerBarnes
TylerBarnes merged commit 88b9dc5 into master Nov 14, 2022
@TylerBarnes
TylerBarnes deleted the chore/wp-switch-to-individual-exports-gatsby-node branch November 14, 2022 22:53
@LekoArts LekoArts added topic: source-wordpress Related to Gatsby's integration with WordPress topic: source-plugins Relates to the Gatsby source plugins (e.g. -filesystem) and removed status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer labels Nov 16, 2022
raffishquartan pushed a commit to raffishquartan/gatsby that referenced this pull request Apr 28, 2026
…Steps for each gatsby-node api (gatsbyjs#37039)

remove runApisInSteps and call runApiSteps for each gatsby-node api
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

topic: source-plugins Relates to the Gatsby source plugins (e.g. -filesystem) topic: source-wordpress Related to Gatsby's integration with WordPress

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants