vscode-graphql, LSP, IDE initiative

[acao]

Getting things in better shape for vscode-graphql which I am now maintainer of!

graphql-language-service-interface

• finish upgrading to graphq-config@3.0.x - schema loading, file loading, etc
• new options argument for getAutocompleteSuggestions
  • allow use of implicit fragment definitions for completion
  • option to return all completion options on empty or even invalid input (ala codemirror-graphql, etc)
• getOutline for workspaces
• getDefinition for workspaces
• when autocompleting a field that expands:
  • automatically append {}
  • move cursor inside new brackets (this part may require monoco/vscode-languageserver)
  • automatically complete for descending required fields on enter? (might be for monaco or vscode-languageserver)

graphql-language-service-server

• offset outline/definitions positions for embedded graphql
• build caches for all files immediately on initialization and on each relevant workspace folder/file event, or at least cache all definitions on onRequestWorkspaceSymbol. use invalidateCache()
• handle RequestWorkspaceDefinition event similarly
• supporting the last two might require more configuration on the extension side as well

vscode-graphql

is becoming our go-to reference implementation, and this work is towards 3.x.x releases:

• vscode-graphql@3.0.0

external issues:

• graphql-config endpoints extension no longer supports env, so we still have to figure out how to replace use of env

[felippepuhle]

@acao is there a way we can implement customValidationRules? We're using Relay and I was thinking what's the best way to create an extension for this case.

We already have a lot of validation rules here, we just need to extract them on a generic way.

I'm a nvim user and I created coc-graphql a few weeks ago. CoC plugins have basically the same config as any other vscode plugin, it shouldn't be hard to reuse the same code on both plugins.

[acao]

@felippepuhle awesome! very excited about coc-graphql. i just cut an alpha of the lsp server last night that should be quite an enhancement!

customValidationRules can be defined in the graphql-config that's picked up by the LSP server. here's where we apply them

graphiql/packages/graphql-language-service-interface/src/GraphQLLanguageService.ts

Line 198 in 7dfaef7

extensions?.customValidationRules &&

previously, it would load from a specified file path, but in graphql-config@3 we support commonjs. so now you can require() a file that provides an array of custom rules, or you can define them implicitly in the graphql.config.js file, your choice!

[felippepuhle]

That's awesome! I'll take a look ASAP, thanks!

[tvvignesh]

@acao The extension is becoming way better than it used to be thanks. But one important thing which I am looking for is support for Federation: #2351

Any plans for the same?

[acao]

@tvvignesh this is possible now that i've squashed some bugs i introduced during this initiative!

[acao]

the follow up!
#2062