cuelsp
cuelsp copied to clipboard
dagger
An attempt at including formatting to the LSP. I'm quite new to LSP implementation, not sure if there's a standard for passing options to the formatter. I'll dig a bit...
### What is the issue? I just installed the VSCode extension v0.3.2 but the extension crashes on me. VSCode info: Version: 1.69.2 Commit: 3b889b090b5ad5793f524b5d1d39fda662b96a2a Date: 2022-07-18T16:12:57.074Z (1 wk ago) Electron:...
### What are you trying to do? I want to find an elegant way to handle error globally without any code duplication ### Why is this important to you? It's...
There is a companion plugin to vim-lsp that automatically creates configuration for vim-lsp. We should add our contribution: [mattn/vim-lsp-settings](https://github.com/mattn/vim-lsp-settings) Then we won't have to create configuration documentation other than >...
Dagger plan always follows the same logic: 1 - Define your action 2 - Create or call definition To improve user experience, we could integrate code snippet in the LSP,...
It's common for a LSP to integrate file formatting, Dagger LSP should not be an exception. When user press command to format file, Dagger LSP should execute `cue fmt` function...
The next step after #42 is dynamic completion. For example, if a definition `#Foo` is written in the plan, when the user type `#Fo`, Dagger LSP should propose `#Foo` and...
As a LSP, it's primordial to enhance user productivity through multiples helpers. One of them is the completion. It's a really strong tool that helps write things faster and reduce...
That would be useful to see how a value is constructed. For instance ```cue #Definition: { foo: string } #Embed: { #Definition bar: number } ``` Will produce the result...
It looks important to handle this method to stop the server : https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#exit