Something that would put a huge smile on my face would be a ‘LSP update’ for Nova. I admittedly don’t know the first thing about prioritising features for a text editor, but maintaining the royal road to the many ecosystems with language servers seems like it has a good bang:buck ratio.
To me it feels like Nova is so close, and it’s that last 2% that marks the threshold between “this feels great” and “maybe I should just use VScode… (sad face)”.
I don’t regret the time I’ve put into my own Deno LSP extension, but I’d think twice about putting more in. I’m probably not alone in that.
Panic likely have something much more comprehensive than this, but for my own curiosity I assembled a little list of all the LSP issues I could find on this forum. Seeing them all lined up this made me think that really great LSP experience might not be too far away?
Not implemented
- onRequest (LanguageClient onRequest isn't being called - #4 by robb-j)
- workspace/executeCommand (LSP method `workspace/executeCommand` isn't implemented - #5 by jo-te)
- registerCapability (LSP import action error)
- Additional edit/command support (Language Server CompletionItem additional edit/command support)
- Rendering multiple returned content blocks Nova doesn't display all editor hover content
- Virtual LSP definitions Opening 'virtual' LSP definitions
Bugs
- textDocument/didSave not being sent - have to do it manually (textDocument/didSave notification not being sent - #5 by mike.bronner)
- textDocument/codeAction range error on last line (LSP: textDocument/codeAction CodeActionParams with wrong Range - #2 by drew)
- textDocument/didChange range error on last line (LSP: textDocument/codeAction CodeActionParams with wrong Range - #2 by drew)
- textDocument/completion (Bug with textDocument/completion)
Enhancements
- LSP markdown not rendering as expected (Language Server: Markdown not rendering properly)