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

query depth for validate does not match audit #2698

Open
4 tasks
shawnjones253 opened this issue Mar 15, 2024 · 1 comment
Open
4 tasks

query depth for validate does not match audit #2698

shawnjones253 opened this issue Mar 15, 2024 · 1 comment

Comments

@shawnjones253
Copy link

Issue workflow progress

Progress of the issue based on the
Contributor Workflow

  • 1. The issue provides a reproduction available on GitHub, Stackblitz or CodeSandbox

    Make sure to fork this template and run pnpm generate in the terminal.

    Please make sure the Codegen and plugins version under package.json matches yours.

  • 2. A failing test has been provided
  • 3. A local solution has been provided
  • 4. A pull request is pending review

Describe the bug

I've got a report produced by graphql-inspector audit './**/*.tsx' (gql template literals in the tsx files).

Several of the queries and mutations report a depth of 20.

When I run the same files through graphql-inspector validate './**/*.tsx' './schema.graphql' --maxDepth 8 --errorsOnly I get no failures.

To Reproduce Steps to reproduce the behavior:
I'm happy to send my schema and docuements directly to someone but would rather not post them publicly.

Expected behavior

Environment:

  • OS:
  • @graphql-inspector/...:
  • graphql:
  • NodeJS:

Additional context

@Minishlink
Copy link

I'm also encountering this problem. Probably because validate doesn't handle fragments the same as audit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants