Adam Boniecki

Examples of how new CLASP package is referenced in other projects: > Eg. razor - [razor/src/Razor/src/Microsoft.AspNetCore.Razor.LanguageServer/Microsoft.AspNetCore.Razor.LanguageServer.csproj at 6ada92f5fc25f916afccc41d3dce2c618d9fcd11 · dotnet/razor (github.com)](https://github.com/dotnet/razor/blob/6ada92f5fc25f916afccc41d3dce2c618d9fcd11/src/Razor/src/Microsoft.AspNetCore.Razor.LanguageServer/Microsoft.AspNetCore.Razor.LanguageServer.csproj#L26) or webtools - https://devdiv.visualstudio.com/DevDiv/_git/VS?path=/src/Xaml/Designer/Source/CodeAnalysis/CodeAnalysis.csproj&version=GBmain&line=26&lineEnd=27&lineStartColumn=1&lineEndColumn=1&lineStyle=plain&_a=contents

In FSI, an invalid string literal can break further parsing of string in that interactive session

8

In FSI, inputting an interpolated string literal that opens interpolation expression with `{` but does not close it, e.g. `$"{"` breaks the session in a way that further valid string...

## Description We need to implement the `textDocument/completion` endpoint as defined by the [Language Server Protocol specification](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/). This endpoint is responsible for providing intelligent code completions at a given cursor...

Implement the `textDocument/definition` endpoint for the F# LSP server. This endpoint will provide the "go to definition" functionality. The LSP specification for this endpoint can be found under [this link](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_definition)....

Move the WIP LSP extension to the common vsix

1

First step in resolving #18067