ionide/LanguageServerProtocol

This system is an F\# library that provides core abstractions for implementing Language Server Protocol (LSP) clients and servers. It utilizes StreamJsonRpc for asynchronous communication and includes a code generation tool to create type definitions and interfaces from the LSP meta model. The project also features a comprehensive test suite for validating serialization roundtrips, server startup stability, and performance benchmarks.

This change establishes the foundational project structure, introducing the solution file, F\# project files, and a Directory.Build.targets file that integrates Fantomas for automatic code formatting during the build process. It also adds configuration files including .editorconfig for consistent coding styles, .gitattributes and .gitignore for repository hygiene, and a global.json pinning the .NET SDK version. Documentation is updated with a CONTRIBUTING guide detailing the release process and a README providing build instructions and examples of language servers built with the library.

(repo-wide) · high confidence

This change introduces the foundational \LspClient\ and \LspServer\ abstract classes, along with the \ILspClient\ and \ILspServer\ interfaces, which define the contract for Language Server Protocol communication. It replaces the previous transport mechanism with \StreamJsonRpc\, enabling asynchronous request and notification handling via \AsyncLspResult\. The update includes a comprehensive logging infrastructure (\FsLibLog\) and custom JSON serialization utilities (such as \OptionConverter\ and strict type converters) to ensure robust data exchange between the client and server.

src · high confidence

A new command-line tool, MetaModelGenerator, has been added to the tools directory to generate F\# source code from the LSP meta model. The tool provides two commands: 'Types' to generate type definitions and 'ClientServer' to generate client and server interfaces, utilizing System.Text.Json for deserialization and Fantomas for code formatting.

tools · high confidence

Added a new test suite in the \tests\ directory that validates the Language Server Protocol implementation. This includes \Shotgun.fs\ for property-based roundtrip serialization tests of all LSP types using FsCheck, \Tests.fs\ for detailed unit tests on JSON serialization behaviors (such as mutable fields and extension data), \Benchmarks.fs\ for performance testing of type checking logic, and \StartWithSetup.fs\ for verifying server startup stability and graceful handling of JSON parse errors.

tests · high confidence

This change introduces the core project files for the Language Server Protocol library, establishing the build and dependency baseline. The main library (Ionide.LanguageServerProtocol) targets .NET Standard 2.0 and relies on Newtonsoft.Json (13.0.1), System.Text.Json (10.0.8), and StreamJsonRpc (2.16.36), while also pinning FSharp.Core to 6.0.0. A new MetaModelGenerator tool is added, targeting .NET 10.0 and using Fabulous.AST (1.2.0) to generate types from the LSP meta model. Additionally, a test project is created targeting .NET 8.0 and 10.0, utilizing Expecto (10.2.1), FsCheck (2.16.5), and BenchmarkDotNet (0.13.1) for validation and performance testing.

(dependencies) · high confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 57 → 56 (-1.1)
• Rubric changed (rubric-2026.09.15 → rubric-2026.10.1) — scores are not directly comparable.

• Code Health 88 → 88 (+0.0)
• Architecture 100 → 100 (+0.1)
• Maturity 38 → 38 (+0.0)
• Readiness 62 → 62 (+0.0)
• Security 78 → 73 (-4.5)
• Performance 75 (new)

• Documentation: no contributor guidance (README.md)
• Documentation: no installation or build instructions (README.md)
• Documentation: no usage examples (README.md)
• Off-boarding risk: anonymized user #1

• Off-boarding risk: anonymized user #1

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

ionide/LanguageServerProtocol was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.