[graphql-vscode] Language server does not update schema cache if `graphql-config.load.rootDir` does not contain schema file

[benatshippabo]

Description

Whenever graphql-config.load.rootDir does not contain the schema file, the language server does not pick up schema file changes.

Example setting:

{
  "graphql-config.load.rootDir": "configs"
}

Example fs:

.
├── .vscode
│  └── settings.json
├── configs
│  └── .graphqlrc.yml
├── README.md
├── schema.graphql
└── src
   ├── mutation.graphql
   └── query.graphql

Note

The above example is just to demonstrate the bug, realistically we have something such as:

.
├── frontend
│  ├── .graphqlrc.yml
│  └── operations
└── server
   ├── .graphqlrc.yml
   ├── operations
   ├── resolvers
   └── schema.graphql

And since we cannot have multiple projects until #2616 we take the loss and just let the extension language server parse operations in the frontend folder.

Reproduction

https://github.com/benatshippabo/graphql-vscode-bug

Suggestion

Haven't looked at the code yet, but maybe we can just put a watcher on the schema file.

cf: https://discord.com/channels/625400653321076807/863688262181453845/1020491480634249317

[benatshippabo]

@acao any news on this? If you could point us in the right direction, we may be able to assist as well

[acao]

hey @benatshippabo - i was busy with work at the time, and now have been busy because of mass layoffs, but i may have a sponsor soon to help advance work on the LSP. We are currently focused on other parts of the ecosystem, but the LSP server is a possible target for our work. Otherwise, it may take a few months for me to get back to this!

The work required to fix this issue without causing massive over-fetching is significant. I know what I plan to do, but it will take time. It involves the existing schema cacheing mechanism, but there are issues baked in there that require a significant rewrite of the LSP server