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

feat(gatsby-source-wordpress): Fix false positive error if the URL and the responsePath are the same #31612

Merged
merged 1 commit into from
May 28, 2021

Conversation

dhoko
Copy link
Contributor

@dhoko dhoko commented May 27, 2021

👋

Description

It is possible to get this output from the response:

{
  "responsePath": "https://<xxx>/graphql",
  "path": "/graphql",
  "url": "https://<xxx>/graphql"
}

instead of

{
  "responsePath": "/graphql",
  "path": "/graphql",
  "url": "https://<xxx>/graphql"
}

It doesn't make sense to reject the request with the error: GraphQL request was redirected
as the responsePath is the url.

I tried this fix to build my website, and it works fine.

It is possible to get this output from the response:
{
  responsePath: 'https://<xxx>/graphql',
  path: '/graphql',
  url: 'https://<xxx>/graphql'
}
instead of
{
  responsePath: '/graphql',
  path: '/graphql',
  url: 'https://<xxx>/graphql'
}

It doesn't make sense to reject the request with GraphQL request was redirected
as the responsePath _is_ the url.
@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label May 27, 2021
@dhoko dhoko changed the title Fix false positive error if the URL and the responsePath are the same feat(gatsby-source-wordpress) Fix false positive error if the URL and the responsePath are the same May 27, 2021
@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 May 28, 2021
@TylerBarnes
Copy link
Contributor

Thanks for this!

@TylerBarnes TylerBarnes changed the title feat(gatsby-source-wordpress) Fix false positive error if the URL and the responsePath are the same feat(gatsby-source-wordpress): Fix false positive error if the URL and the responsePath are the same May 28, 2021
@TylerBarnes TylerBarnes merged commit cca71cf into gatsbyjs:master May 28, 2021
moonmeister added a commit to moonmeister/gatsby that referenced this pull request Jun 1, 2021
* master: (23 commits)
  fix(gatsby-source-wordpress): Prevent "EADDRINUSE: address already in use 127.0.0.1" error (gatsbyjs#31713)
  feat(gatsby-source-wordpress: architecture.md (gatsbyjs#31537)
  chore(deps): update dependency @babel/node to ^7.14.2 (gatsbyjs#31690)
  chore(deps): update babel monorepo (gatsbyjs#31143)
  fix(gatsby): merge resolveType when merging abstract types (gatsbyjs#31710)
  chore(release): Publish next
  fix(gatsby): Correct config for svgo plugins whitelist
  chore: Add translations and validations to Contentful test (gatsbyjs#31533)
  chore(docs): Correct nginx spelling (gatsbyjs#31651)
  chore(docs): Update Jest instructions for v27 (gatsbyjs#31649)
  Fix typo in adding-search.md (gatsbyjs#31639)
  Fix typos in improving-build-performance.md (gatsbyjs#31640)
  feat(gatsby-source-wordpress): Fix false positive error if the URL and the responsePath are the same (gatsbyjs#31612)
  Fixed syntax error in example (gatsbyjs#31636)
  fix(contentful): pass reporter to retry function (gatsbyjs#31608)
  chore: Properly typecheck `gatsby` (gatsbyjs#31519)
  fix(gatsby-source-contentful): fix progress bar (gatsbyjs#31467)
  fix(gatsby-plugin-gatsby-cloud): fix cloud being bundled (gatsbyjs#31604)
  chore(gatsby-source-wordpress): Fix typos (gatsbyjs#31600)
  chore(docs): Add title to release notes (gatsbyjs#31595)
  ...
pragmaticpat pushed a commit to pragmaticpat/gatsby that referenced this pull request Apr 28, 2022
…d the responsePath are the same (gatsbyjs#31612)

It is possible to get this output from the response:
{
  responsePath: 'https://<xxx>/graphql',
  path: '/graphql',
  url: 'https://<xxx>/graphql'
}
instead of
{
  responsePath: '/graphql',
  path: '/graphql',
  url: 'https://<xxx>/graphql'
}

It doesn't make sense to reject the request with GraphQL request was redirected
as the responsePath _is_ the url.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: source-wordpress Related to Gatsby's integration with WordPress
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants