lsp-types

lsp-types copied to clipboard

many types don't derive Hash even though they can

1

many types (for example: `Position` and `Range`) don't derive `Hash`. this makes it hard to use these types if a `HashMap` is needed, without using intermediate types. is there a...

pickx

Currently `CompletionItemCapabilityResolveSupport` is stringly typed but is there any reason why it isn't made to accept types rather than have it stringly typed?

pickfire

jrmuizel

minor doc issue

ratmice

Investigate: Use expectorate and schemafy to autogenerate code

3

https://github.com/deathbeds/expectorate can give us a JSON schema of the LSP. See if we can use that in combination with @Marwes schemafy crate to autogenerate the LSP types.

kjeremy

See upcoming LSP addition for Notebook documents: [LSP Notebook Proposal](https://github.com/microsoft/vscode-languageserver-node/blob/815cb9737e8a0f5d9ef7e41dce42f6b771ca24aa/protocol/src/common/proposed.notebooks.md#notebooks) This is a draft for adding notebooks to the spec, see VS Code notebook extension that uses Rust: [Codebook](https://marketplace.visualstudio.com/items?itemName=codebook.codebook) Using...

jackos

When I create `lsp_types::document_symbols::DocumentSymbol`, I always write an extra line `#[allow(deprecated)]` to suppress deprecated lint message. These symbols also have no constructor. I think we can implement Default for these...

oovm

Error when deserializing notification

1

I have a `didSave` notification from the SublimeText LSP plugin which looks like this: ``` { "jsonrpc": "2.0", "method": "textDocument/didSave", "params": { "textDocument": { "uri": "file:///Users/spencerkohan/Projects/patina/examples/foo.pt" }, "text": "func foo(x:...

spencerkohan

Do not use u64 for numbers that could be negative

10

Hello, It seems various fields specified as "number" in the lsp spec are set as u64 in the library, for example `SignatureHelp::activeParameter`. While it seems to make sense, there is...

mawww

Returning partial results

2

While doing #155 I realized that only semantic tokens can handle a partial result in it's `Request::Result`. Would it make sense to add a new trait for requests that can...

kjeremy