Syntax error in typeDefs

[Mangatt]

Actual Behavior

Simple typeDefs.gql file throws Syntax Error: Expected Name, found "}".GraphQL: Syntax

type Test {
	id: ID!
}

type Query {
	test(id: ID!): Test
}

Expected Behavior

There should not be an error.

Steps to Reproduce the Problem Or Description

Create file with contents above.

Specifications

• GraphQL for VSCode Extension Version: 0.3.41
• VSCode Version: 1.63.2
• OS Name: Win 10
• OS Version: 21H2
• graphql config filename and format example: .graphqlrc

{
  "schema": "http://localhost:4000/graphql",
  "documents": "packages/*/src/**/*.{graphql,gql,js,ts,jsx,tsx}",
  "extensions": {
  	"endpoints": {
  		"default": {
  			"url": "http://localhost:4000"
  		}
  	}
  }
}

Logs Of TS Server || GraphQL Language Service

[ragokan]

I am having same error

[acao]

thanks for the heads up! this might have to do with the graphql-config upgrade.

moving to the LSP repository since this is related to the language server

[acao]

@Mangatt @ragokan to explain what is happening, graphql-config loadDocuments() on startup and on file save events is scanning your entire documents tree, and throws an exception when parsing an incomplete graphql string in a file that isn't even open in vscode.

Note that this only happens when documents config option is used.

This is because graphql-config uses graphql-tools loaders which use graphql-js parse() under the hood, thus the familiar graphql validation error. There are a lot of efficiencies we hope to introduce here but its hard to test the dozens of edge cases every time.

So for now, we just need to trap and ignore graphql-config loadDocuments() exceptions

@dotansimha how do you suggest we handle these exceptions moving forward?

When we use our internal findGraphQLTags implementation, we use graphql-language-service-parser to parse all the files and build object/fragment/etc definition caches, which handles incomplete graphql strings

[mmmulani]

I'm running into this issue with a .graphqlrc.yml file of:

# .graphqlrc.yml
schema: "shared/schema.graphql"

where documents is not specified but instead a single schema file is.

Anyone have a workaround for this? It doesn't seem like there's a setting in the graphql extension but possibly vscode has a setting to disable showing these errors?