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

check command failed if schema is not available #418

Open
3 tasks done
oceandrama opened this issue Nov 21, 2024 · 1 comment
Open
3 tasks done

check command failed if schema is not available #418

oceandrama opened this issue Nov 21, 2024 · 1 comment

Comments

@oceandrama
Copy link

Describe the bug

It looks like check command should only validate queries with existing introspection (and it works exactly like this), but before that it also checks for schema availability, which may not be possible, for example, in ci/cd without internet access. I think this is unneccesary step, which may be skipped

Reproduction

No response

gql.tada version

gql.tada v1.8.10

Validations

  • I can confirm that this is a bug report, and not a feature request, RFC, question, or discussion, for which GitHub Discussions should be used
  • Read the docs.
  • Follow our Code of Conduct
@kitten
Copy link
Member

kitten commented Nov 21, 2024

The check command is able to output any diagnostics that the GraphQLSP plugin outputs in your editor/IDE. As such, it needs the schema and operates on schema-based validation rules as well.

If your schema isn't permanently available (for example if it's built up and/or stored in a different repo) you may want to consider downloading it and committing it to your repo: https://gql-tada.0no.co/get-started/workflows#downloading-schemas

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