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

Missing field argument lead to broken Documentation Explorer #3115

Closed
2 of 3 tasks
datproto opened this issue May 1, 2024 · 2 comments
Closed
2 of 3 tasks

Missing field argument lead to broken Documentation Explorer #3115

datproto opened this issue May 1, 2024 · 2 comments
Labels
Needs: Reproduction This issue needs to be reproduced independently.

Comments

@datproto
Copy link

datproto commented May 1, 2024

Description

When upgrading the wpgraphql to 1.24.0, the document cannot be loaded due to missing some field argument.
This lead to the broken of Documentation Explorer (please check image attachment below).

Steps to reproduce

  1. Install wpgraphql version 1.24.0
  2. Open GraphiQL IDE
  3. The error appear at the preview window right at the start

image

Additional context

Other installed wpgraphql:

  • WPGraphQL IDE: 1.1.8
  • WPGraphQL for ACF: 2.2.0
  • WPGraphQL Smart Cache: 1.3.2
  • WPGraphQL for Gravity Forms: 0.12.6
  • WPGraphQL JWT Authentication: 0.7.0
  • WPGraphQL WooCommerce (WooGraphQL): 0.19.0

WPGraphQL Version

1.24.0

WordPress Version

6.5.2

PHP Version

8.1

Additional environment details

No response

Please confirm that you have searched existing issues in the repo.

  • Yes

Please confirm that you have disabled ALL plugins except for WPGraphQL.

  • Yes
  • My issue is with compatibility with a specific WordPress plugin, and I have listed all my installed plugins (and version info) above.
@justlevine
Copy link
Collaborator

(sounds like a duplicate of #3108 )

@josephfusco josephfusco added the Needs: Reproduction This issue needs to be reproduced independently. label May 1, 2024
@jasonbahl
Copy link
Collaborator

@datproto closing as this is being tracked in #3108. We're close to having a fix ready for release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs: Reproduction This issue needs to be reproduced independently.
Projects
Status: Done
Development

No branches or pull requests

4 participants