No language features for .graphql files since v0.5.0 (only colorization)

I’ve been trying to make the latest versions of this extension to work but it seems like completion (and most other language features) broke since v0.5.0. Note that everything works fine in v0.4.15.

The project I’m currently working on is here, in case you want to check out my setup. But as a summary, my graphql.config.json file looks like this:

{
    "schema": "./graphql-server/introspection.json",
    "documents": "./graphql-server/**/*.graphql"
}

And I’m using codegen with the following configuration:

schema: './graphql-server/schema.ts'
documents: './graphql-server/**/*.graphql'
generates:
  ./graphql-server/introspection.json:
    plugins:
      - introspection
    config:
      minify: true
  ./graphql-server/sdk.ts:
    plugins:
      - add:
          content: '// @ts-nocheck Ignore this file, it is just codegen output'
      - typescript
      - typescript-operations
      - typescript-graphql-request
      - plugin-typescript-swr
    config:
      skipTypename: true
  ./graphql-server/resolvers-types.ts:
    plugins:
      - add:
          content: '// @ts-nocheck Ignore this file, it is just codegen output'
      - typescript
      - typescript-resolvers

The logs only show the following:

8/14/2022, 2:55:11 PM [3] (pid: 7005) graphql-language-service-usage-logs: {"type":"usage","messageType":"initialize"}

[MariaSolOs]

@MariaSolOs another clue, i suspect maybe logic I introduced with cacheProjectFiles() in messageprocessor could have caused some issues here

@acao So I’m not sure if it is a caching issue per se, but I think I have a fix 😃 #2720

[MariaSolOs]

Okay so I have an update: After debugging for a bit today I discovered that the problem is not parseDocument but in getTokenAtPosition. The returned token is not correct, resulting in whack completions that don’t apply to the cursor’s position.

As an example, I was comparing the behaviour in v0.4.15 versus the current one with the following mutation:

mutation createSnippet(
    $name: String!, 
    $description: String!
) {
    createSnippet(
        name: $name, 
        description: $description
    ) {
        id
        | <- cursor triggering completions
    }
}

In v0.4.15, the kind of this token would be Field, but now it is Document.