The graphqls extension is not accepted as an introspection output
See original GitHub issueWhile I can use the .graphqls extension for documents, I can’t use it for the schema file in the validate command:
$ graphql-inspector validate "src/**/*.graphqls" schema.graphql
success All documents are valid
$ graphql-inspector validate "src/**/*.graphql" schema.graphqls
error Unable to find matching files for glob: schema.graphqls in directory: .
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
GraphQL schema introspection failure on newer version of ...
Expected Behavior GraphQL schema introspection succeeded. ... description: 'Marks an element of a GraphQL schema as no longer supported.
Read more >Introspection - GraphQL
A query language for your API — GraphQL provides a complete description of the data in your API, gives clients the power to...
Read more >Three ways to represent your GraphQL schema
The GraphQL Schema Definition Language, or SDL; The GraphQL introspection query result; The GraphQL.js GraphQLSchema object. First, let's dive ...
Read more >GraphQL: Language Feature Support
Extension for Visual Studio Code - GraphQL LSP extension that adds autocompletion, validation, go to definition, hover, outline and more.
Read more >introspection - GraphQL Code Generator
yarn add -D @graphql-codegen/introspection. This plugin generates a GraphQL introspection file based on your GraphQL schema.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Weird, I can’t reproduce it either right now. I recently re-installed the cli so maybe that was the issue or something was wrong on my end. Thanks a lot for checking.
Thanks so much for fixing!