GraphQL LanguageService 3.0.0 Roadmap

[acao]

With monaco, we can start working more directly with our complete Language Server Protocol library (GraphQLLanguageService in interface), which can be consumed by everyone on the web and in their IDE.

Introducing monaco will require some underlying changes to the languageservice, as well as introducing LSP spec language features.

Package Re-organization

• graphql-languageservice (new) - a glue package for interface and types. meant to re-create the pattern of other vscode LS packages. More details
• graphql-language-service-interface
• graphql-language-service-parser

TODO

• convert to TS
• Symbols
• interfaces implementing interfaces
• Go To Definition (single document)
• Go To Definition (full workspace)
• Find References
• Go To Reference
• Plugins in the interface?
• Adopt upcoming 15.0.x features
• Replace @babel/parser with a language agnostic parser for gql template tags and other configurable patterns.
• Universal file system
• Universal config, graphql-config?

[divyenduz]

Go To Definition (full workspace)

This already works for a file that you open in the editor once. Maybe this is just about building the catch at first launch once.