Hello, I'm fairly sure that this is a bug, but I'm not 100% sure.
Anyway, when my editor sends a textDocument/hover request to roc-ls, the response is a a MarkedString, which should contain Markdown, but roc-ls seems to assume that it will be interpreted as plaintext. For example, I wrote the function f = \{field1, field2} -> {}, and when I hovered over the function name, roc-ls returned the response:
My editor (neovim, built-in lsp client) seems to process this as markdown (as the lsp specification says it should), and showed me text that looked like this: { field1 : , field2 : * } -> {}.
Apparently using MarkedString is deprecated anyway, and the new approach is to use MarkupContent, which supports a plaintext option.
Hello, I'm fairly sure that this is a bug, but I'm not 100% sure.
Anyway, when my editor sends a
textDocument/hover
request toroc-ls
, the response is a aMarkedString
, which should contain Markdown, butroc-ls
seems to assume that it will be interpreted as plaintext. For example, I wrote the functionf = \{field1, field2} -> {}
, and when I hovered over the function name,roc-ls
returned the response:My editor (neovim, built-in lsp client) seems to process this as markdown (as the lsp specification says it should), and showed me text that looked like this:
{ field1 : , field2 : * } -> {}
.Apparently using
MarkedString
is deprecated anyway, and the new approach is to useMarkupContent
, which supports a plaintext option.The relevant code, I think