Language Server Roadmap

[JoshuaBatty]

Currently, the language server only enables a very small subset of features. Features such as hover, rename, go_to definition, and highlight were disabled before #2121 was recently merged. However, as a result of that PR we now have the infrastructure in place to move ahead with a plan for properly supporting them again. I wanted to open an issue that outlines the order of tasks that we have planned for better LSP support.

As more issues are created I will update this list to reflect them.

• Create a pipeline allowing the client to request custom data from the server
• Reorganize language server to handle full projects instead of single files #2318
• Start using the typed AST tokens in the language server #2319
• Use the thiserror crate and report any internal language server errors to the client #2286
• improve LSP dealing with imports #324
• Support the LSP go_to definition capability #2259
• Add autocomplete support for expr.  #2408
• Sway LSP should not allow renaming keywords or tokens from std #1418
• Support the LSP highlighting capability #2258
• Support the LSP rename capability #2261
• Support the LSP hover capability showing type info and doc comments #2260
• Add Inline Type Hints to Sway-Server #111
• Extend LSP and VSCode plugin with DAP debugger support #1864

[JoshuaBatty]

Closing in favor of using the new LSP + IDEs project view https://github.com/orgs/FuelLabs/projects/21/views/1