Executive summary
razzmatazz/csharp-language-server falls short of our standard for a preview release, in part because the project keeps no record of its design decisions. It scores 59 out of 100 and is rated Adequate, and ten of its 12 critical findings are security problems.
Maturity, at 50, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 9 points. Bringing the documentation in line with the code is another step, worth about 7 points. Raising Maturity to 62 would lift the score to about 65.
Eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Pinning each tool to an exact version would close this risk. The two checks for vulnerable packages switched off need switching back on. The two sets of compiler warnings switched off in projects need turning back on in the build file.
The product code is 22,225 lines, about €36,000 to rebuild.
If Maturity rose from 50 to 62, the lowest score rated Strong, the score would rise from 59 to about 65.
New since the last survey: 2 findings
- Code Duplication · Edited copy of a member (23 corresponding lines) src/CSharpLanguageServer/Handlers/Color.fs
- Code Duplication · Edited copies of one member (6 members, 20+ corresponding lines) src/CSharpLanguageServer/Handlers/Declaration.fs
Rebuild cost: about €36,000 · Estimate
| Cost to rebuild | €12,000 to €60,000, for 199 to 630 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 59. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 22,225 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Ionide.LanguageServerProtocol.JsonRpc | 2 Ionide.LanguageServerProtocol.Logging.Types | 3 Ionide.LanguageServerProtocol.Types | 4 MetaModelGenerator.MetaModel | 5 Ionide.LanguageServerProtocol | 6 CSharpLanguageServer.Types | 7 CSharpLanguageServer.Diagnostics | 8 CSharpLanguageServer.Lsp.Client | 9 CSharpLanguageServer.Lsp.WorkspaceFolder | 10 CSharpLanguageServer.Lsp.Workspace | 11 CSharpLanguageServer.Runtime.RequestScheduling | 12 CSharpLanguageServer.Handlers.CallHierarchy | 13 CSharpLanguageServer.Handlers.CodeAction | 14 CSharpLanguageServer.Handlers.CodeLens | 15 CSharpLanguageServer.Handlers.Color | 16 CSharpLanguageServer.Handlers.Completion | 17 CSharpLanguageServer.Handlers.Declaration | 18 CSharpLanguageServer.Handlers.Definition | 19 CSharpLanguageServer.Handlers.Diagnostic | 20 CSharpLanguageServer.Handlers.DocumentFormatting | 21 CSharpLanguageServer.Handlers.DocumentHighlight | 22 CSharpLanguageServer.Handlers.DocumentLink | 23 CSharpLanguageServer.Handlers.DocumentOnTypeFormatting | 24 CSharpLanguageServer.Handlers.DocumentRangeFormatting | 25 CSharpLanguageServer.Handlers.DocumentSymbol | 26 CSharpLanguageServer.Handlers.ExecuteCommand | 27 CSharpLanguageServer.Handlers.FoldingRange | 28 CSharpLanguageServer.Handlers.Hover | 29 CSharpLanguageServer.Handlers.Implementation | 30 CSharpLanguageServer.Handlers.InlayHint | 31 CSharpLanguageServer.Handlers.InlineValue | 32 CSharpLanguageServer.Handlers.LifeCycle | 33 CSharpLanguageServer.Handlers.Rename | 34 CSharpLanguageServer.Handlers.SemanticTokens | 35 CSharpLanguageServer.Handlers.TextDocumentSync | 36 CSharpLanguageServer.Handlers.Workspace | 37 CSharpLanguageServer.Runtime.DebugInfo | 38 CSharpLanguageServer.Runtime.PushDiagnostics | 39 CSharpLanguageServer.Runtime.ServerStateLoop | 40 CSharpLanguageServer.Lsp.Server |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Ionide.LanguageServerProtocol.JsonRpc | ||||||||||||||||||||||||||||||||||||||||
| 2 Ionide.LanguageServerProtocol.Logging.Types | ||||||||||||||||||||||||||||||||||||||||
| 3 Ionide.LanguageServerProtocol.Types | ||||||||||||||||||||||||||||||||||||||||
| 4 MetaModelGenerator.MetaModel | ||||||||||||||||||||||||||||||||||||||||
| 5 Ionide.LanguageServerProtocol | 4 | 238 | ||||||||||||||||||||||||||||||||||||||
| 6 CSharpLanguageServer.Types | 2 | 24 | 3 | |||||||||||||||||||||||||||||||||||||
| 7 CSharpLanguageServer.Diagnostics | 1 | 19 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 8 CSharpLanguageServer.Lsp.Client | 1 | 15 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 9 CSharpLanguageServer.Lsp.WorkspaceFolder | 3 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 10 CSharpLanguageServer.Lsp.Workspace | 5 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 11 CSharpLanguageServer.Runtime.RequestScheduling | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 12 CSharpLanguageServer.Handlers.CallHierarchy | 8 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 13 CSharpLanguageServer.Handlers.CodeAction | 7 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 14 CSharpLanguageServer.Handlers.CodeLens | 6 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 15 CSharpLanguageServer.Handlers.Color | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 CSharpLanguageServer.Handlers.Completion | 7 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 CSharpLanguageServer.Handlers.Declaration | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 CSharpLanguageServer.Handlers.Definition | 5 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 CSharpLanguageServer.Handlers.Diagnostic | 11 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 20 CSharpLanguageServer.Handlers.DocumentFormatting | 7 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 CSharpLanguageServer.Handlers.DocumentHighlight | 6 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 CSharpLanguageServer.Handlers.DocumentLink | 5 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 CSharpLanguageServer.Handlers.DocumentOnTypeFormatting | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 CSharpLanguageServer.Handlers.DocumentRangeFormatting | 5 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 CSharpLanguageServer.Handlers.DocumentSymbol | 7 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 CSharpLanguageServer.Handlers.ExecuteCommand | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 CSharpLanguageServer.Handlers.FoldingRange | 8 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 CSharpLanguageServer.Handlers.Hover | 6 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 CSharpLanguageServer.Handlers.Implementation | 6 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 CSharpLanguageServer.Handlers.InlayHint | 7 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 CSharpLanguageServer.Handlers.InlineValue | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 CSharpLanguageServer.Handlers.LifeCycle | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 CSharpLanguageServer.Handlers.Rename | 7 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 CSharpLanguageServer.Handlers.SemanticTokens | 1 | 10 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 CSharpLanguageServer.Handlers.TextDocumentSync | 11 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 CSharpLanguageServer.Handlers.Workspace | 6 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 CSharpLanguageServer.Runtime.DebugInfo | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 38 CSharpLanguageServer.Runtime.PushDiagnostics | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 CSharpLanguageServer.Runtime.ServerStateLoop | 5 | 2 | 3 | 1 | 2 | 5 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 40 CSharpLanguageServer.Lsp.Server | 4 | 1 | 1 |
5→1 Ionide.LanguageServerProtocol uses Ionide.LanguageServerProtocol.JsonRpc✕
- Connections
- 4 pairs of types, where a type in Ionide.LanguageServerProtocol uses a type in Ionide.LanguageServerProtocol.JsonRpc.
- The types involved
Ionide.LanguageServerProtocol.ILspClient→Ionide.LanguageServerProtocol.JsonRpc.ErrorIonide.LanguageServerProtocol.ILspServer→Ionide.LanguageServerProtocol.JsonRpc.ErrorIonide.LanguageServerProtocol.LspClient→Ionide.LanguageServerProtocol.JsonRpc.ErrorIonide.LanguageServerProtocol.LspServer→Ionide.LanguageServerProtocol.JsonRpc.Error
- Direction
- Ionide.LanguageServerProtocol uses Ionide.LanguageServerProtocol.JsonRpc, so a change to Ionide.LanguageServerProtocol.JsonRpc can break Ionide.LanguageServerProtocol, while a change to Ionide.LanguageServerProtocol can't break Ionide.LanguageServerProtocol.JsonRpc.
- Position
- Below the diagonal: Ionide.LanguageServerProtocol uses a module listed above it, which is the healthy direction.
5→3 Ionide.LanguageServerProtocol uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 238 pairs of types, where a type in Ionide.LanguageServerProtocol uses a type in Ionide.LanguageServerProtocol.Types. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Ionide.LanguageServerProtocol.ILspClient→Ionide.LanguageServerProtocol.Types.ApplyWorkspaceEditParamsIonide.LanguageServerProtocol.ILspClient→Ionide.LanguageServerProtocol.Types.ApplyWorkspaceEditResultIonide.LanguageServerProtocol.ILspClient→Ionide.LanguageServerProtocol.Types.CancelParamsIonide.LanguageServerProtocol.ILspClient→Ionide.LanguageServerProtocol.Types.ConfigurationParamsIonide.LanguageServerProtocol.ILspClient→Ionide.LanguageServerProtocol.Types.LSPAnyIonide.LanguageServerProtocol.ILspClient→Ionide.LanguageServerProtocol.Types.LogMessageParamsIonide.LanguageServerProtocol.ILspClient→Ionide.LanguageServerProtocol.Types.LogTraceParamsIonide.LanguageServerProtocol.ILspClient→Ionide.LanguageServerProtocol.Types.MessageActionItemIonide.LanguageServerProtocol.ILspClient→Ionide.LanguageServerProtocol.Types.ProgressParamsIonide.LanguageServerProtocol.ILspClient→Ionide.LanguageServerProtocol.Types.PublishDiagnosticsParamsIonide.LanguageServerProtocol.ILspClient→Ionide.LanguageServerProtocol.Types.RegistrationParamsIonide.LanguageServerProtocol.ILspClient→Ionide.LanguageServerProtocol.Types.ShowDocumentParamsIonide.LanguageServerProtocol.ILspClient→Ionide.LanguageServerProtocol.Types.ShowDocumentResultIonide.LanguageServerProtocol.ILspClient→Ionide.LanguageServerProtocol.Types.ShowMessageParamsIonide.LanguageServerProtocol.ILspClient→Ionide.LanguageServerProtocol.Types.ShowMessageRequestParamsIonide.LanguageServerProtocol.ILspClient→Ionide.LanguageServerProtocol.Types.UnregistrationParamsIonide.LanguageServerProtocol.ILspClient→Ionide.LanguageServerProtocol.Types.WorkDoneProgressCreateParamsIonide.LanguageServerProtocol.ILspClient→Ionide.LanguageServerProtocol.Types.WorkspaceFolderIonide.LanguageServerProtocol.ILspServer→Ionide.LanguageServerProtocol.Types.CallHierarchyIncomingCallIonide.LanguageServerProtocol.ILspServer→Ionide.LanguageServerProtocol.Types.CallHierarchyIncomingCallsParamsIonide.LanguageServerProtocol.ILspServer→Ionide.LanguageServerProtocol.Types.CallHierarchyItemIonide.LanguageServerProtocol.ILspServer→Ionide.LanguageServerProtocol.Types.CallHierarchyOutgoingCallIonide.LanguageServerProtocol.ILspServer→Ionide.LanguageServerProtocol.Types.CallHierarchyOutgoingCallsParamsIonide.LanguageServerProtocol.ILspServer→Ionide.LanguageServerProtocol.Types.CallHierarchyPrepareParamsIonide.LanguageServerProtocol.ILspServer→Ionide.LanguageServerProtocol.Types.CancelParams
- Direction
- Ionide.LanguageServerProtocol uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break Ionide.LanguageServerProtocol, while a change to Ionide.LanguageServerProtocol can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: Ionide.LanguageServerProtocol uses a module listed above it, which is the healthy direction.
6→1 CSharpLanguageServer.Types uses Ionide.LanguageServerProtocol.JsonRpc✕
- Connections
- 2 pairs of types, where a type in CSharpLanguageServer.Types uses a type in Ionide.LanguageServerProtocol.JsonRpc.
- The types involved
CSharpLanguageServer.Types.DisconnectedLspClient→Ionide.LanguageServerProtocol.JsonRpc.ErrorCSharpLanguageServer.Types.ICSharpLspServer→Ionide.LanguageServerProtocol.JsonRpc.Error
- Direction
- CSharpLanguageServer.Types uses Ionide.LanguageServerProtocol.JsonRpc, so a change to Ionide.LanguageServerProtocol.JsonRpc can break CSharpLanguageServer.Types, while a change to CSharpLanguageServer.Types can't break Ionide.LanguageServerProtocol.JsonRpc.
- Position
- Below the diagonal: CSharpLanguageServer.Types uses a module listed above it, which is the healthy direction.
6→3 CSharpLanguageServer.Types uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 24 pairs of types, where a type in CSharpLanguageServer.Types uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Types.CSharpMetadataParams→Ionide.LanguageServerProtocol.Types.TextDocumentIdentifierCSharpLanguageServer.Types.DisconnectedLspClient→Ionide.LanguageServerProtocol.Types.ApplyWorkspaceEditParamsCSharpLanguageServer.Types.DisconnectedLspClient→Ionide.LanguageServerProtocol.Types.ApplyWorkspaceEditResultCSharpLanguageServer.Types.DisconnectedLspClient→Ionide.LanguageServerProtocol.Types.CancelParamsCSharpLanguageServer.Types.DisconnectedLspClient→Ionide.LanguageServerProtocol.Types.ConfigurationParamsCSharpLanguageServer.Types.DisconnectedLspClient→Ionide.LanguageServerProtocol.Types.LSPAnyCSharpLanguageServer.Types.DisconnectedLspClient→Ionide.LanguageServerProtocol.Types.LogMessageParamsCSharpLanguageServer.Types.DisconnectedLspClient→Ionide.LanguageServerProtocol.Types.LogTraceParamsCSharpLanguageServer.Types.DisconnectedLspClient→Ionide.LanguageServerProtocol.Types.MessageActionItemCSharpLanguageServer.Types.DisconnectedLspClient→Ionide.LanguageServerProtocol.Types.ProgressParamsCSharpLanguageServer.Types.DisconnectedLspClient→Ionide.LanguageServerProtocol.Types.PublishDiagnosticsParamsCSharpLanguageServer.Types.DisconnectedLspClient→Ionide.LanguageServerProtocol.Types.RegistrationParamsCSharpLanguageServer.Types.DisconnectedLspClient→Ionide.LanguageServerProtocol.Types.ShowDocumentParamsCSharpLanguageServer.Types.DisconnectedLspClient→Ionide.LanguageServerProtocol.Types.ShowDocumentResultCSharpLanguageServer.Types.DisconnectedLspClient→Ionide.LanguageServerProtocol.Types.ShowMessageParamsCSharpLanguageServer.Types.DisconnectedLspClient→Ionide.LanguageServerProtocol.Types.ShowMessageRequestParamsCSharpLanguageServer.Types.DisconnectedLspClient→Ionide.LanguageServerProtocol.Types.UnregistrationParamsCSharpLanguageServer.Types.DisconnectedLspClient→Ionide.LanguageServerProtocol.Types.WorkDoneProgressCreateParamsCSharpLanguageServer.Types.DisconnectedLspClient→Ionide.LanguageServerProtocol.Types.WorkspaceFolderCSharpLanguageServer.Types.ICSharpLspClient→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Types.Types→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Types.Types→Ionide.LanguageServerProtocol.Types.NotebookCellTextDocumentFilterCSharpLanguageServer.Types.Types→Ionide.LanguageServerProtocol.Types.TextDocumentFilterCSharpLanguageServer.Types.Types→Ionide.LanguageServerProtocol.Types.U2`2
- Direction
- CSharpLanguageServer.Types uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Types, while a change to CSharpLanguageServer.Types can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Types uses a module listed above it, which is the healthy direction.
6→5 CSharpLanguageServer.Types uses Ionide.LanguageServerProtocol✕
- Connections
- 3 pairs of types, where a type in CSharpLanguageServer.Types uses a type in Ionide.LanguageServerProtocol.
- The types involved
CSharpLanguageServer.Types.DisconnectedLspClient→Ionide.LanguageServerProtocol.ILspClientCSharpLanguageServer.Types.ICSharpLspClient→Ionide.LanguageServerProtocol.ILspClientCSharpLanguageServer.Types.ICSharpLspServer→Ionide.LanguageServerProtocol.ILspServer
- Direction
- CSharpLanguageServer.Types uses Ionide.LanguageServerProtocol, so a change to Ionide.LanguageServerProtocol can break CSharpLanguageServer.Types, while a change to CSharpLanguageServer.Types can't break Ionide.LanguageServerProtocol.
- Position
- Below the diagonal: CSharpLanguageServer.Types uses a module listed above it, which is the healthy direction.
7→1 CSharpLanguageServer.Diagnostics uses Ionide.LanguageServerProtocol.JsonRpc✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Diagnostics uses a type in Ionide.LanguageServerProtocol.JsonRpc.
- The types involved
CSharpLanguageServer.Diagnostics.LspClientStub→Ionide.LanguageServerProtocol.JsonRpc.Error
- Direction
- CSharpLanguageServer.Diagnostics uses Ionide.LanguageServerProtocol.JsonRpc, so a change to Ionide.LanguageServerProtocol.JsonRpc can break CSharpLanguageServer.Diagnostics, while a change to CSharpLanguageServer.Diagnostics can't break Ionide.LanguageServerProtocol.JsonRpc.
- Position
- Below the diagonal: CSharpLanguageServer.Diagnostics uses a module listed above it, which is the healthy direction.
7→3 CSharpLanguageServer.Diagnostics uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 19 pairs of types, where a type in CSharpLanguageServer.Diagnostics uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Diagnostics.Diagnostics→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Diagnostics.LspClientStub→Ionide.LanguageServerProtocol.Types.ApplyWorkspaceEditParamsCSharpLanguageServer.Diagnostics.LspClientStub→Ionide.LanguageServerProtocol.Types.ApplyWorkspaceEditResultCSharpLanguageServer.Diagnostics.LspClientStub→Ionide.LanguageServerProtocol.Types.CancelParamsCSharpLanguageServer.Diagnostics.LspClientStub→Ionide.LanguageServerProtocol.Types.ConfigurationParamsCSharpLanguageServer.Diagnostics.LspClientStub→Ionide.LanguageServerProtocol.Types.LSPAnyCSharpLanguageServer.Diagnostics.LspClientStub→Ionide.LanguageServerProtocol.Types.LogMessageParamsCSharpLanguageServer.Diagnostics.LspClientStub→Ionide.LanguageServerProtocol.Types.LogTraceParamsCSharpLanguageServer.Diagnostics.LspClientStub→Ionide.LanguageServerProtocol.Types.MessageActionItemCSharpLanguageServer.Diagnostics.LspClientStub→Ionide.LanguageServerProtocol.Types.ProgressParamsCSharpLanguageServer.Diagnostics.LspClientStub→Ionide.LanguageServerProtocol.Types.PublishDiagnosticsParamsCSharpLanguageServer.Diagnostics.LspClientStub→Ionide.LanguageServerProtocol.Types.RegistrationParamsCSharpLanguageServer.Diagnostics.LspClientStub→Ionide.LanguageServerProtocol.Types.ShowDocumentParamsCSharpLanguageServer.Diagnostics.LspClientStub→Ionide.LanguageServerProtocol.Types.ShowDocumentResultCSharpLanguageServer.Diagnostics.LspClientStub→Ionide.LanguageServerProtocol.Types.ShowMessageParamsCSharpLanguageServer.Diagnostics.LspClientStub→Ionide.LanguageServerProtocol.Types.ShowMessageRequestParamsCSharpLanguageServer.Diagnostics.LspClientStub→Ionide.LanguageServerProtocol.Types.UnregistrationParamsCSharpLanguageServer.Diagnostics.LspClientStub→Ionide.LanguageServerProtocol.Types.WorkDoneProgressCreateParamsCSharpLanguageServer.Diagnostics.LspClientStub→Ionide.LanguageServerProtocol.Types.WorkspaceFolder
- Direction
- CSharpLanguageServer.Diagnostics uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Diagnostics, while a change to CSharpLanguageServer.Diagnostics can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Diagnostics uses a module listed above it, which is the healthy direction.
7→5 CSharpLanguageServer.Diagnostics uses Ionide.LanguageServerProtocol✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Diagnostics uses a type in Ionide.LanguageServerProtocol.
- The types involved
CSharpLanguageServer.Diagnostics.LspClientStub→Ionide.LanguageServerProtocol.ILspClient
- Direction
- CSharpLanguageServer.Diagnostics uses Ionide.LanguageServerProtocol, so a change to Ionide.LanguageServerProtocol can break CSharpLanguageServer.Diagnostics, while a change to CSharpLanguageServer.Diagnostics can't break Ionide.LanguageServerProtocol.
- Position
- Below the diagonal: CSharpLanguageServer.Diagnostics uses a module listed above it, which is the healthy direction.
7→6 CSharpLanguageServer.Diagnostics uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Diagnostics uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Diagnostics.Diagnostics→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Diagnostics uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Diagnostics, while a change to CSharpLanguageServer.Diagnostics can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Diagnostics uses a module listed above it, which is the healthy direction.
8→1 CSharpLanguageServer.Lsp.Client uses Ionide.LanguageServerProtocol.JsonRpc✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Lsp.Client uses a type in Ionide.LanguageServerProtocol.JsonRpc.
- The types involved
CSharpLanguageServer.Lsp.Client.CSharpLspClient→Ionide.LanguageServerProtocol.JsonRpc.Error
- Direction
- CSharpLanguageServer.Lsp.Client uses Ionide.LanguageServerProtocol.JsonRpc, so a change to Ionide.LanguageServerProtocol.JsonRpc can break CSharpLanguageServer.Lsp.Client, while a change to CSharpLanguageServer.Lsp.Client can't break Ionide.LanguageServerProtocol.JsonRpc.
- Position
- Below the diagonal: CSharpLanguageServer.Lsp.Client uses a module listed above it, which is the healthy direction.
8→3 CSharpLanguageServer.Lsp.Client uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 15 pairs of types, where a type in CSharpLanguageServer.Lsp.Client uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Lsp.Client.CSharpLspClient→Ionide.LanguageServerProtocol.Types.ApplyWorkspaceEditParamsCSharpLanguageServer.Lsp.Client.CSharpLspClient→Ionide.LanguageServerProtocol.Types.ApplyWorkspaceEditResultCSharpLanguageServer.Lsp.Client.CSharpLspClient→Ionide.LanguageServerProtocol.Types.ConfigurationParamsCSharpLanguageServer.Lsp.Client.CSharpLspClient→Ionide.LanguageServerProtocol.Types.LSPAnyCSharpLanguageServer.Lsp.Client.CSharpLspClient→Ionide.LanguageServerProtocol.Types.LogMessageParamsCSharpLanguageServer.Lsp.Client.CSharpLspClient→Ionide.LanguageServerProtocol.Types.LogTraceParamsCSharpLanguageServer.Lsp.Client.CSharpLspClient→Ionide.LanguageServerProtocol.Types.MessageActionItemCSharpLanguageServer.Lsp.Client.CSharpLspClient→Ionide.LanguageServerProtocol.Types.ProgressParamsCSharpLanguageServer.Lsp.Client.CSharpLspClient→Ionide.LanguageServerProtocol.Types.PublishDiagnosticsParamsCSharpLanguageServer.Lsp.Client.CSharpLspClient→Ionide.LanguageServerProtocol.Types.RegistrationParamsCSharpLanguageServer.Lsp.Client.CSharpLspClient→Ionide.LanguageServerProtocol.Types.ShowMessageParamsCSharpLanguageServer.Lsp.Client.CSharpLspClient→Ionide.LanguageServerProtocol.Types.ShowMessageRequestParamsCSharpLanguageServer.Lsp.Client.CSharpLspClient→Ionide.LanguageServerProtocol.Types.UnregistrationParamsCSharpLanguageServer.Lsp.Client.CSharpLspClient→Ionide.LanguageServerProtocol.Types.WorkDoneProgressCreateParamsCSharpLanguageServer.Lsp.Client.CSharpLspClient→Ionide.LanguageServerProtocol.Types.WorkspaceFolder
- Direction
- CSharpLanguageServer.Lsp.Client uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Lsp.Client, while a change to CSharpLanguageServer.Lsp.Client can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Lsp.Client uses a module listed above it, which is the healthy direction.
8→5 CSharpLanguageServer.Lsp.Client uses Ionide.LanguageServerProtocol✕
- Connections
- 2 pairs of types, where a type in CSharpLanguageServer.Lsp.Client uses a type in Ionide.LanguageServerProtocol.
- The types involved
CSharpLanguageServer.Lsp.Client.CSharpLspClient→Ionide.LanguageServerProtocol.ILspClientCSharpLanguageServer.Lsp.Client.CSharpLspClient→Ionide.LanguageServerProtocol.LspClient
- Direction
- CSharpLanguageServer.Lsp.Client uses Ionide.LanguageServerProtocol, so a change to Ionide.LanguageServerProtocol can break CSharpLanguageServer.Lsp.Client, while a change to CSharpLanguageServer.Lsp.Client can't break Ionide.LanguageServerProtocol.
- Position
- Below the diagonal: CSharpLanguageServer.Lsp.Client uses a module listed above it, which is the healthy direction.
8→6 CSharpLanguageServer.Lsp.Client uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Lsp.Client uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Lsp.Client.CSharpLspClient→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Lsp.Client uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Lsp.Client, while a change to CSharpLanguageServer.Lsp.Client can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Lsp.Client uses a module listed above it, which is the healthy direction.
9→3 CSharpLanguageServer.Lsp.WorkspaceFolder uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 3 pairs of types, where a type in CSharpLanguageServer.Lsp.WorkspaceFolder uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Lsp.WorkspaceFolder.WorkspaceFolder→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Lsp.WorkspaceFolder.WorkspaceFolder→Ionide.LanguageServerProtocol.Types.LocationCSharpLanguageServer.Lsp.WorkspaceFolder.WorkspaceFolder→Ionide.LanguageServerProtocol.Types.Position
- Direction
- CSharpLanguageServer.Lsp.WorkspaceFolder uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Lsp.WorkspaceFolder, while a change to CSharpLanguageServer.Lsp.WorkspaceFolder can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Lsp.WorkspaceFolder uses a module listed above it, which is the healthy direction.
9→5 CSharpLanguageServer.Lsp.WorkspaceFolder uses Ionide.LanguageServerProtocol✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Lsp.WorkspaceFolder uses a type in Ionide.LanguageServerProtocol.
- The types involved
CSharpLanguageServer.Lsp.WorkspaceFolder.WorkspaceFolder→Ionide.LanguageServerProtocol.ILspClient
- Direction
- CSharpLanguageServer.Lsp.WorkspaceFolder uses Ionide.LanguageServerProtocol, so a change to Ionide.LanguageServerProtocol can break CSharpLanguageServer.Lsp.WorkspaceFolder, while a change to CSharpLanguageServer.Lsp.WorkspaceFolder can't break Ionide.LanguageServerProtocol.
- Position
- Below the diagonal: CSharpLanguageServer.Lsp.WorkspaceFolder uses a module listed above it, which is the healthy direction.
9→6 CSharpLanguageServer.Lsp.WorkspaceFolder uses CSharpLanguageServer.Types✕
- Connections
- 2 pairs of types, where a type in CSharpLanguageServer.Lsp.WorkspaceFolder uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Lsp.WorkspaceFolder.LspWorkspaceDecompiledMetadataDocument→CSharpLanguageServer.Types.CSharpMetadataInformationCSharpLanguageServer.Lsp.WorkspaceFolder.WorkspaceFolder→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Lsp.WorkspaceFolder uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Lsp.WorkspaceFolder, while a change to CSharpLanguageServer.Lsp.WorkspaceFolder can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Lsp.WorkspaceFolder uses a module listed above it, which is the healthy direction.
10→3 CSharpLanguageServer.Lsp.Workspace uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 5 pairs of types, where a type in CSharpLanguageServer.Lsp.Workspace uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Lsp.Workspace.LspWorkspaceUpdate→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Lsp.Workspace.LspWorkspaceUpdate→Ionide.LanguageServerProtocol.Types.TraceValuesCSharpLanguageServer.Lsp.Workspace.LspWorkspaceUpdate→Ionide.LanguageServerProtocol.Types.WorkspaceFolderCSharpLanguageServer.Lsp.Workspace.Workspace→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Lsp.Workspace.Workspace→Ionide.LanguageServerProtocol.Types.WorkspaceFolder
- Direction
- CSharpLanguageServer.Lsp.Workspace uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Lsp.Workspace, while a change to CSharpLanguageServer.Lsp.Workspace can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Lsp.Workspace uses a module listed above it, which is the healthy direction.
10→5 CSharpLanguageServer.Lsp.Workspace uses Ionide.LanguageServerProtocol✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Lsp.Workspace uses a type in Ionide.LanguageServerProtocol.
- The types involved
CSharpLanguageServer.Lsp.Workspace.Workspace→Ionide.LanguageServerProtocol.ILspClient
- Direction
- CSharpLanguageServer.Lsp.Workspace uses Ionide.LanguageServerProtocol, so a change to Ionide.LanguageServerProtocol can break CSharpLanguageServer.Lsp.Workspace, while a change to CSharpLanguageServer.Lsp.Workspace can't break Ionide.LanguageServerProtocol.
- Position
- Below the diagonal: CSharpLanguageServer.Lsp.Workspace uses a module listed above it, which is the healthy direction.
10→6 CSharpLanguageServer.Lsp.Workspace uses CSharpLanguageServer.Types✕
- Connections
- 2 pairs of types, where a type in CSharpLanguageServer.Lsp.Workspace uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Lsp.Workspace.LspWorkspaceUpdate→CSharpLanguageServer.Types.CSharpConfigurationCSharpLanguageServer.Lsp.Workspace.Workspace→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Lsp.Workspace uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Lsp.Workspace, while a change to CSharpLanguageServer.Lsp.Workspace can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Lsp.Workspace uses a module listed above it, which is the healthy direction.
10→9 CSharpLanguageServer.Lsp.Workspace uses CSharpLanguageServer.Lsp.WorkspaceFolder✕
- Connections
- 2 pairs of types, where a type in CSharpLanguageServer.Lsp.Workspace uses a type in CSharpLanguageServer.Lsp.WorkspaceFolder.
- The types involved
CSharpLanguageServer.Lsp.Workspace.LspWorkspace→CSharpLanguageServer.Lsp.WorkspaceFolder.LspWorkspaceFolderCSharpLanguageServer.Lsp.Workspace.Workspace→CSharpLanguageServer.Lsp.WorkspaceFolder.LspWorkspaceFolder
- Direction
- CSharpLanguageServer.Lsp.Workspace uses CSharpLanguageServer.Lsp.WorkspaceFolder, so a change to CSharpLanguageServer.Lsp.WorkspaceFolder can break CSharpLanguageServer.Lsp.Workspace, while a change to CSharpLanguageServer.Lsp.Workspace can't break CSharpLanguageServer.Lsp.WorkspaceFolder.
- Position
- Below the diagonal: CSharpLanguageServer.Lsp.Workspace uses a module listed above it, which is the healthy direction.
11→3 CSharpLanguageServer.Runtime.RequestScheduling uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Runtime.RequestScheduling uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Runtime.RequestScheduling.RequestContext→Ionide.LanguageServerProtocol.Types.ClientCapabilities
- Direction
- CSharpLanguageServer.Runtime.RequestScheduling uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Runtime.RequestScheduling, while a change to CSharpLanguageServer.Runtime.RequestScheduling can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Runtime.RequestScheduling uses a module listed above it, which is the healthy direction.
11→5 CSharpLanguageServer.Runtime.RequestScheduling uses Ionide.LanguageServerProtocol✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Runtime.RequestScheduling uses a type in Ionide.LanguageServerProtocol.
- The types involved
CSharpLanguageServer.Runtime.RequestScheduling.RequestContext→Ionide.LanguageServerProtocol.ILspClient
- Direction
- CSharpLanguageServer.Runtime.RequestScheduling uses Ionide.LanguageServerProtocol, so a change to Ionide.LanguageServerProtocol can break CSharpLanguageServer.Runtime.RequestScheduling, while a change to CSharpLanguageServer.Runtime.RequestScheduling can't break Ionide.LanguageServerProtocol.
- Position
- Below the diagonal: CSharpLanguageServer.Runtime.RequestScheduling uses a module listed above it, which is the healthy direction.
11→6 CSharpLanguageServer.Runtime.RequestScheduling uses CSharpLanguageServer.Types✕
- Connections
- 2 pairs of types, where a type in CSharpLanguageServer.Runtime.RequestScheduling uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Runtime.RequestScheduling.RequestContext→CSharpLanguageServer.Types.CSharpConfigurationCSharpLanguageServer.Runtime.RequestScheduling.RequestScheduling→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Runtime.RequestScheduling uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Runtime.RequestScheduling, while a change to CSharpLanguageServer.Runtime.RequestScheduling can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Runtime.RequestScheduling uses a module listed above it, which is the healthy direction.
11→9 CSharpLanguageServer.Runtime.RequestScheduling uses CSharpLanguageServer.Lsp.WorkspaceFolder✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Runtime.RequestScheduling uses a type in CSharpLanguageServer.Lsp.WorkspaceFolder.
- The types involved
CSharpLanguageServer.Runtime.RequestScheduling.RequestContext→CSharpLanguageServer.Lsp.WorkspaceFolder.LspWorkspaceFolder
- Direction
- CSharpLanguageServer.Runtime.RequestScheduling uses CSharpLanguageServer.Lsp.WorkspaceFolder, so a change to CSharpLanguageServer.Lsp.WorkspaceFolder can break CSharpLanguageServer.Runtime.RequestScheduling, while a change to CSharpLanguageServer.Runtime.RequestScheduling can't break CSharpLanguageServer.Lsp.WorkspaceFolder.
- Position
- Below the diagonal: CSharpLanguageServer.Runtime.RequestScheduling uses a module listed above it, which is the healthy direction.
12→3 CSharpLanguageServer.Handlers.CallHierarchy uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 8 pairs of types, where a type in CSharpLanguageServer.Handlers.CallHierarchy uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Handlers.CallHierarchy.CallHierarchy→Ionide.LanguageServerProtocol.Types.CallHierarchyIncomingCallsParamsCSharpLanguageServer.Handlers.CallHierarchy.CallHierarchy→Ionide.LanguageServerProtocol.Types.CallHierarchyOptionsCSharpLanguageServer.Handlers.CallHierarchy.CallHierarchy→Ionide.LanguageServerProtocol.Types.CallHierarchyOutgoingCallsParamsCSharpLanguageServer.Handlers.CallHierarchy.CallHierarchy→Ionide.LanguageServerProtocol.Types.CallHierarchyPrepareParamsCSharpLanguageServer.Handlers.CallHierarchy.CallHierarchy→Ionide.LanguageServerProtocol.Types.CallHierarchyRegistrationOptionsCSharpLanguageServer.Handlers.CallHierarchy.CallHierarchy→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Handlers.CallHierarchy.CallHierarchy→Ionide.LanguageServerProtocol.Types.RegistrationCSharpLanguageServer.Handlers.CallHierarchy.CallHierarchy→Ionide.LanguageServerProtocol.Types.U3`3
- Direction
- CSharpLanguageServer.Handlers.CallHierarchy uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Handlers.CallHierarchy, while a change to CSharpLanguageServer.Handlers.CallHierarchy can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.CallHierarchy uses a module listed above it, which is the healthy direction.
12→6 CSharpLanguageServer.Handlers.CallHierarchy uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.CallHierarchy uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Handlers.CallHierarchy.CallHierarchy→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Handlers.CallHierarchy uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Handlers.CallHierarchy, while a change to CSharpLanguageServer.Handlers.CallHierarchy can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.CallHierarchy uses a module listed above it, which is the healthy direction.
12→11 CSharpLanguageServer.Handlers.CallHierarchy uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.CallHierarchy uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Handlers.CallHierarchy.CallHierarchy→CSharpLanguageServer.Runtime.RequestScheduling.RequestContext
- Direction
- CSharpLanguageServer.Handlers.CallHierarchy uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Handlers.CallHierarchy, while a change to CSharpLanguageServer.Handlers.CallHierarchy can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.CallHierarchy uses a module listed above it, which is the healthy direction.
13→3 CSharpLanguageServer.Handlers.CodeAction uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 7 pairs of types, where a type in CSharpLanguageServer.Handlers.CodeAction uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Handlers.CodeAction.CodeAction→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Handlers.CodeAction.CodeAction→Ionide.LanguageServerProtocol.Types.CodeActionCSharpLanguageServer.Handlers.CodeAction.CodeAction→Ionide.LanguageServerProtocol.Types.CodeActionOptionsCSharpLanguageServer.Handlers.CodeAction.CodeAction→Ionide.LanguageServerProtocol.Types.CodeActionParamsCSharpLanguageServer.Handlers.CodeAction.CodeAction→Ionide.LanguageServerProtocol.Types.RegistrationCSharpLanguageServer.Handlers.CodeAction.CodeAction→Ionide.LanguageServerProtocol.Types.TextDocumentEditCSharpLanguageServer.Handlers.CodeAction.CodeAction→Ionide.LanguageServerProtocol.Types.U2`2
- Direction
- CSharpLanguageServer.Handlers.CodeAction uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Handlers.CodeAction, while a change to CSharpLanguageServer.Handlers.CodeAction can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.CodeAction uses a module listed above it, which is the healthy direction.
13→6 CSharpLanguageServer.Handlers.CodeAction uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.CodeAction uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Handlers.CodeAction.CodeAction→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Handlers.CodeAction uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Handlers.CodeAction, while a change to CSharpLanguageServer.Handlers.CodeAction can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.CodeAction uses a module listed above it, which is the healthy direction.
13→9 CSharpLanguageServer.Handlers.CodeAction uses CSharpLanguageServer.Lsp.WorkspaceFolder✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.CodeAction uses a type in CSharpLanguageServer.Lsp.WorkspaceFolder.
- The types involved
CSharpLanguageServer.Handlers.CodeAction.CodeAction→CSharpLanguageServer.Lsp.WorkspaceFolder.LspWorkspaceFolder
- Direction
- CSharpLanguageServer.Handlers.CodeAction uses CSharpLanguageServer.Lsp.WorkspaceFolder, so a change to CSharpLanguageServer.Lsp.WorkspaceFolder can break CSharpLanguageServer.Handlers.CodeAction, while a change to CSharpLanguageServer.Handlers.CodeAction can't break CSharpLanguageServer.Lsp.WorkspaceFolder.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.CodeAction uses a module listed above it, which is the healthy direction.
13→11 CSharpLanguageServer.Handlers.CodeAction uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.CodeAction uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Handlers.CodeAction.CodeAction→CSharpLanguageServer.Runtime.RequestScheduling.RequestContext
- Direction
- CSharpLanguageServer.Handlers.CodeAction uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Handlers.CodeAction, while a change to CSharpLanguageServer.Handlers.CodeAction can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.CodeAction uses a module listed above it, which is the healthy direction.
14→3 CSharpLanguageServer.Handlers.CodeLens uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 6 pairs of types, where a type in CSharpLanguageServer.Handlers.CodeLens uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Handlers.CodeLens.CodeLens→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Handlers.CodeLens.CodeLens→Ionide.LanguageServerProtocol.Types.CodeLensCSharpLanguageServer.Handlers.CodeLens.CodeLens→Ionide.LanguageServerProtocol.Types.CodeLensOptionsCSharpLanguageServer.Handlers.CodeLens.CodeLens→Ionide.LanguageServerProtocol.Types.CodeLensParamsCSharpLanguageServer.Handlers.CodeLens.CodeLens→Ionide.LanguageServerProtocol.Types.RegistrationCSharpLanguageServer.Handlers.CodeLens.CodeLensData→Ionide.LanguageServerProtocol.Types.Position
- Direction
- CSharpLanguageServer.Handlers.CodeLens uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Handlers.CodeLens, while a change to CSharpLanguageServer.Handlers.CodeLens can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.CodeLens uses a module listed above it, which is the healthy direction.
14→6 CSharpLanguageServer.Handlers.CodeLens uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.CodeLens uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Handlers.CodeLens.CodeLens→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Handlers.CodeLens uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Handlers.CodeLens, while a change to CSharpLanguageServer.Handlers.CodeLens can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.CodeLens uses a module listed above it, which is the healthy direction.
14→11 CSharpLanguageServer.Handlers.CodeLens uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.CodeLens uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Handlers.CodeLens.CodeLens→CSharpLanguageServer.Runtime.RequestScheduling.RequestContext
- Direction
- CSharpLanguageServer.Handlers.CodeLens uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Handlers.CodeLens, while a change to CSharpLanguageServer.Handlers.CodeLens can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.CodeLens uses a module listed above it, which is the healthy direction.
15→3 CSharpLanguageServer.Handlers.Color uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 4 pairs of types, where a type in CSharpLanguageServer.Handlers.Color uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Handlers.Color.Color→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Handlers.Color.Color→Ionide.LanguageServerProtocol.Types.ColorPresentationParamsCSharpLanguageServer.Handlers.Color.Color→Ionide.LanguageServerProtocol.Types.DocumentColorParamsCSharpLanguageServer.Handlers.Color.Color→Ionide.LanguageServerProtocol.Types.Registration
- Direction
- CSharpLanguageServer.Handlers.Color uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Handlers.Color, while a change to CSharpLanguageServer.Handlers.Color can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Color uses a module listed above it, which is the healthy direction.
15→6 CSharpLanguageServer.Handlers.Color uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.Color uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Handlers.Color.Color→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Handlers.Color uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Handlers.Color, while a change to CSharpLanguageServer.Handlers.Color can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Color uses a module listed above it, which is the healthy direction.
15→11 CSharpLanguageServer.Handlers.Color uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.Color uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Handlers.Color.Color→CSharpLanguageServer.Runtime.RequestScheduling.RequestContext
- Direction
- CSharpLanguageServer.Handlers.Color uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Handlers.Color, while a change to CSharpLanguageServer.Handlers.Color can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Color uses a module listed above it, which is the healthy direction.
16→3 CSharpLanguageServer.Handlers.Completion uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 7 pairs of types, where a type in CSharpLanguageServer.Handlers.Completion uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Handlers.Completion.Completion→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Handlers.Completion.Completion→Ionide.LanguageServerProtocol.Types.CompletionContextCSharpLanguageServer.Handlers.Completion.Completion→Ionide.LanguageServerProtocol.Types.CompletionItemCSharpLanguageServer.Handlers.Completion.Completion→Ionide.LanguageServerProtocol.Types.CompletionItemKindCSharpLanguageServer.Handlers.Completion.Completion→Ionide.LanguageServerProtocol.Types.CompletionOptionsCSharpLanguageServer.Handlers.Completion.Completion→Ionide.LanguageServerProtocol.Types.CompletionParamsCSharpLanguageServer.Handlers.Completion.Completion→Ionide.LanguageServerProtocol.Types.Registration
- Direction
- CSharpLanguageServer.Handlers.Completion uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Handlers.Completion, while a change to CSharpLanguageServer.Handlers.Completion can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Completion uses a module listed above it, which is the healthy direction.
16→6 CSharpLanguageServer.Handlers.Completion uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.Completion uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Handlers.Completion.Completion→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Handlers.Completion uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Handlers.Completion, while a change to CSharpLanguageServer.Handlers.Completion can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Completion uses a module listed above it, which is the healthy direction.
16→11 CSharpLanguageServer.Handlers.Completion uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.Completion uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Handlers.Completion.Completion→CSharpLanguageServer.Runtime.RequestScheduling.RequestContext
- Direction
- CSharpLanguageServer.Handlers.Completion uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Handlers.Completion, while a change to CSharpLanguageServer.Handlers.Completion can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Completion uses a module listed above it, which is the healthy direction.
17→3 CSharpLanguageServer.Handlers.Declaration uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 3 pairs of types, where a type in CSharpLanguageServer.Handlers.Declaration uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Handlers.Declaration.Declaration→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Handlers.Declaration.Declaration→Ionide.LanguageServerProtocol.Types.DeclarationParamsCSharpLanguageServer.Handlers.Declaration.Declaration→Ionide.LanguageServerProtocol.Types.Registration
- Direction
- CSharpLanguageServer.Handlers.Declaration uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Handlers.Declaration, while a change to CSharpLanguageServer.Handlers.Declaration can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Declaration uses a module listed above it, which is the healthy direction.
17→6 CSharpLanguageServer.Handlers.Declaration uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.Declaration uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Handlers.Declaration.Declaration→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Handlers.Declaration uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Handlers.Declaration, while a change to CSharpLanguageServer.Handlers.Declaration can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Declaration uses a module listed above it, which is the healthy direction.
17→11 CSharpLanguageServer.Handlers.Declaration uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.Declaration uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Handlers.Declaration.Declaration→CSharpLanguageServer.Runtime.RequestScheduling.RequestContext
- Direction
- CSharpLanguageServer.Handlers.Declaration uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Handlers.Declaration, while a change to CSharpLanguageServer.Handlers.Declaration can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Declaration uses a module listed above it, which is the healthy direction.
18→3 CSharpLanguageServer.Handlers.Definition uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 5 pairs of types, where a type in CSharpLanguageServer.Handlers.Definition uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Handlers.Definition.Definition→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Handlers.Definition.Definition→Ionide.LanguageServerProtocol.Types.DefinitionOptionsCSharpLanguageServer.Handlers.Definition.Definition→Ionide.LanguageServerProtocol.Types.DefinitionParamsCSharpLanguageServer.Handlers.Definition.Definition→Ionide.LanguageServerProtocol.Types.RegistrationCSharpLanguageServer.Handlers.Definition.Definition→Ionide.LanguageServerProtocol.Types.U2`2
- Direction
- CSharpLanguageServer.Handlers.Definition uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Handlers.Definition, while a change to CSharpLanguageServer.Handlers.Definition can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Definition uses a module listed above it, which is the healthy direction.
18→6 CSharpLanguageServer.Handlers.Definition uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.Definition uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Handlers.Definition.Definition→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Handlers.Definition uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Handlers.Definition, while a change to CSharpLanguageServer.Handlers.Definition can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Definition uses a module listed above it, which is the healthy direction.
18→11 CSharpLanguageServer.Handlers.Definition uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.Definition uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Handlers.Definition.Definition→CSharpLanguageServer.Runtime.RequestScheduling.RequestContext
- Direction
- CSharpLanguageServer.Handlers.Definition uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Handlers.Definition, while a change to CSharpLanguageServer.Handlers.Definition can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Definition uses a module listed above it, which is the healthy direction.
19→3 CSharpLanguageServer.Handlers.Diagnostic uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 11 pairs of types, where a type in CSharpLanguageServer.Handlers.Diagnostic uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Handlers.Diagnostic.Diagnostic→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Handlers.Diagnostic.Diagnostic→Ionide.LanguageServerProtocol.Types.DiagnosticOptionsCSharpLanguageServer.Handlers.Diagnostic.Diagnostic→Ionide.LanguageServerProtocol.Types.DiagnosticRegistrationOptionsCSharpLanguageServer.Handlers.Diagnostic.Diagnostic→Ionide.LanguageServerProtocol.Types.DocumentDiagnosticParamsCSharpLanguageServer.Handlers.Diagnostic.Diagnostic→Ionide.LanguageServerProtocol.Types.NotebookCellTextDocumentFilterCSharpLanguageServer.Handlers.Diagnostic.Diagnostic→Ionide.LanguageServerProtocol.Types.RegistrationCSharpLanguageServer.Handlers.Diagnostic.Diagnostic→Ionide.LanguageServerProtocol.Types.TextDocumentFilterCSharpLanguageServer.Handlers.Diagnostic.Diagnostic→Ionide.LanguageServerProtocol.Types.U2`2CSharpLanguageServer.Handlers.Diagnostic.Diagnostic→Ionide.LanguageServerProtocol.Types.WorkspaceDiagnosticParamsCSharpLanguageServer.Handlers.Diagnostic.Diagnostic→Ionide.LanguageServerProtocol.Types.WorkspaceFullDocumentDiagnosticReportCSharpLanguageServer.Handlers.Diagnostic.Diagnostic→Ionide.LanguageServerProtocol.Types.WorkspaceUnchangedDocumentDiagnosticReport
- Direction
- CSharpLanguageServer.Handlers.Diagnostic uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Handlers.Diagnostic, while a change to CSharpLanguageServer.Handlers.Diagnostic can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Diagnostic uses a module listed above it, which is the healthy direction.
19→6 CSharpLanguageServer.Handlers.Diagnostic uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.Diagnostic uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Handlers.Diagnostic.Diagnostic→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Handlers.Diagnostic uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Handlers.Diagnostic, while a change to CSharpLanguageServer.Handlers.Diagnostic can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Diagnostic uses a module listed above it, which is the healthy direction.
19→9 CSharpLanguageServer.Handlers.Diagnostic uses CSharpLanguageServer.Lsp.WorkspaceFolder✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.Diagnostic uses a type in CSharpLanguageServer.Lsp.WorkspaceFolder.
- The types involved
CSharpLanguageServer.Handlers.Diagnostic.Diagnostic→CSharpLanguageServer.Lsp.WorkspaceFolder.LspWorkspaceFolder
- Direction
- CSharpLanguageServer.Handlers.Diagnostic uses CSharpLanguageServer.Lsp.WorkspaceFolder, so a change to CSharpLanguageServer.Lsp.WorkspaceFolder can break CSharpLanguageServer.Handlers.Diagnostic, while a change to CSharpLanguageServer.Handlers.Diagnostic can't break CSharpLanguageServer.Lsp.WorkspaceFolder.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Diagnostic uses a module listed above it, which is the healthy direction.
19→11 CSharpLanguageServer.Handlers.Diagnostic uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.Diagnostic uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Handlers.Diagnostic.Diagnostic→CSharpLanguageServer.Runtime.RequestScheduling.RequestContext
- Direction
- CSharpLanguageServer.Handlers.Diagnostic uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Handlers.Diagnostic, while a change to CSharpLanguageServer.Handlers.Diagnostic can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Diagnostic uses a module listed above it, which is the healthy direction.
20→3 CSharpLanguageServer.Handlers.DocumentFormatting uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 7 pairs of types, where a type in CSharpLanguageServer.Handlers.DocumentFormatting uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Handlers.DocumentFormatting.DocumentFormatting→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Handlers.DocumentFormatting.DocumentFormatting→Ionide.LanguageServerProtocol.Types.DocumentFormattingOptionsCSharpLanguageServer.Handlers.DocumentFormatting.DocumentFormatting→Ionide.LanguageServerProtocol.Types.DocumentFormattingParamsCSharpLanguageServer.Handlers.DocumentFormatting.DocumentFormatting→Ionide.LanguageServerProtocol.Types.FormattingOptionsCSharpLanguageServer.Handlers.DocumentFormatting.DocumentFormatting→Ionide.LanguageServerProtocol.Types.RegistrationCSharpLanguageServer.Handlers.DocumentFormatting.DocumentFormatting→Ionide.LanguageServerProtocol.Types.TextEditCSharpLanguageServer.Handlers.DocumentFormatting.DocumentFormatting→Ionide.LanguageServerProtocol.Types.U2`2
- Direction
- CSharpLanguageServer.Handlers.DocumentFormatting uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Handlers.DocumentFormatting, while a change to CSharpLanguageServer.Handlers.DocumentFormatting can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.DocumentFormatting uses a module listed above it, which is the healthy direction.
20→6 CSharpLanguageServer.Handlers.DocumentFormatting uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.DocumentFormatting uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Handlers.DocumentFormatting.DocumentFormatting→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Handlers.DocumentFormatting uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Handlers.DocumentFormatting, while a change to CSharpLanguageServer.Handlers.DocumentFormatting can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.DocumentFormatting uses a module listed above it, which is the healthy direction.
20→11 CSharpLanguageServer.Handlers.DocumentFormatting uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.DocumentFormatting uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Handlers.DocumentFormatting.DocumentFormatting→CSharpLanguageServer.Runtime.RequestScheduling.RequestContext
- Direction
- CSharpLanguageServer.Handlers.DocumentFormatting uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Handlers.DocumentFormatting, while a change to CSharpLanguageServer.Handlers.DocumentFormatting can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.DocumentFormatting uses a module listed above it, which is the healthy direction.
21→3 CSharpLanguageServer.Handlers.DocumentHighlight uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 6 pairs of types, where a type in CSharpLanguageServer.Handlers.DocumentHighlight uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Handlers.DocumentHighlight.DocumentHighlight→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Handlers.DocumentHighlight.DocumentHighlight→Ionide.LanguageServerProtocol.Types.DocumentHighlightCSharpLanguageServer.Handlers.DocumentHighlight.DocumentHighlight→Ionide.LanguageServerProtocol.Types.DocumentHighlightOptionsCSharpLanguageServer.Handlers.DocumentHighlight.DocumentHighlight→Ionide.LanguageServerProtocol.Types.DocumentHighlightParamsCSharpLanguageServer.Handlers.DocumentHighlight.DocumentHighlight→Ionide.LanguageServerProtocol.Types.RegistrationCSharpLanguageServer.Handlers.DocumentHighlight.DocumentHighlight→Ionide.LanguageServerProtocol.Types.U2`2
- Direction
- CSharpLanguageServer.Handlers.DocumentHighlight uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Handlers.DocumentHighlight, while a change to CSharpLanguageServer.Handlers.DocumentHighlight can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.DocumentHighlight uses a module listed above it, which is the healthy direction.
21→6 CSharpLanguageServer.Handlers.DocumentHighlight uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.DocumentHighlight uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Handlers.DocumentHighlight.DocumentHighlight→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Handlers.DocumentHighlight uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Handlers.DocumentHighlight, while a change to CSharpLanguageServer.Handlers.DocumentHighlight can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.DocumentHighlight uses a module listed above it, which is the healthy direction.
21→11 CSharpLanguageServer.Handlers.DocumentHighlight uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.DocumentHighlight uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Handlers.DocumentHighlight.DocumentHighlight→CSharpLanguageServer.Runtime.RequestScheduling.RequestContext
- Direction
- CSharpLanguageServer.Handlers.DocumentHighlight uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Handlers.DocumentHighlight, while a change to CSharpLanguageServer.Handlers.DocumentHighlight can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.DocumentHighlight uses a module listed above it, which is the healthy direction.
22→3 CSharpLanguageServer.Handlers.DocumentLink uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 5 pairs of types, where a type in CSharpLanguageServer.Handlers.DocumentLink uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Handlers.DocumentLink.DocumentLink→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Handlers.DocumentLink.DocumentLink→Ionide.LanguageServerProtocol.Types.DocumentLinkCSharpLanguageServer.Handlers.DocumentLink.DocumentLink→Ionide.LanguageServerProtocol.Types.DocumentLinkOptionsCSharpLanguageServer.Handlers.DocumentLink.DocumentLink→Ionide.LanguageServerProtocol.Types.DocumentLinkParamsCSharpLanguageServer.Handlers.DocumentLink.DocumentLink→Ionide.LanguageServerProtocol.Types.Registration
- Direction
- CSharpLanguageServer.Handlers.DocumentLink uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Handlers.DocumentLink, while a change to CSharpLanguageServer.Handlers.DocumentLink can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.DocumentLink uses a module listed above it, which is the healthy direction.
22→6 CSharpLanguageServer.Handlers.DocumentLink uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.DocumentLink uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Handlers.DocumentLink.DocumentLink→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Handlers.DocumentLink uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Handlers.DocumentLink, while a change to CSharpLanguageServer.Handlers.DocumentLink can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.DocumentLink uses a module listed above it, which is the healthy direction.
22→11 CSharpLanguageServer.Handlers.DocumentLink uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.DocumentLink uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Handlers.DocumentLink.DocumentLink→CSharpLanguageServer.Runtime.RequestScheduling.RequestContext
- Direction
- CSharpLanguageServer.Handlers.DocumentLink uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Handlers.DocumentLink, while a change to CSharpLanguageServer.Handlers.DocumentLink can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.DocumentLink uses a module listed above it, which is the healthy direction.
23→3 CSharpLanguageServer.Handlers.DocumentOnTypeFormatting uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 4 pairs of types, where a type in CSharpLanguageServer.Handlers.DocumentOnTypeFormatting uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Handlers.DocumentOnTypeFormatting.DocumentOnTypeFormatting→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Handlers.DocumentOnTypeFormatting.DocumentOnTypeFormatting→Ionide.LanguageServerProtocol.Types.DocumentOnTypeFormattingOptionsCSharpLanguageServer.Handlers.DocumentOnTypeFormatting.DocumentOnTypeFormatting→Ionide.LanguageServerProtocol.Types.DocumentOnTypeFormattingParamsCSharpLanguageServer.Handlers.DocumentOnTypeFormatting.DocumentOnTypeFormatting→Ionide.LanguageServerProtocol.Types.Registration
- Direction
- CSharpLanguageServer.Handlers.DocumentOnTypeFormatting uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Handlers.DocumentOnTypeFormatting, while a change to CSharpLanguageServer.Handlers.DocumentOnTypeFormatting can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.DocumentOnTypeFormatting uses a module listed above it, which is the healthy direction.
23→6 CSharpLanguageServer.Handlers.DocumentOnTypeFormatting uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.DocumentOnTypeFormatting uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Handlers.DocumentOnTypeFormatting.DocumentOnTypeFormatting→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Handlers.DocumentOnTypeFormatting uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Handlers.DocumentOnTypeFormatting, while a change to CSharpLanguageServer.Handlers.DocumentOnTypeFormatting can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.DocumentOnTypeFormatting uses a module listed above it, which is the healthy direction.
23→11 CSharpLanguageServer.Handlers.DocumentOnTypeFormatting uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.DocumentOnTypeFormatting uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Handlers.DocumentOnTypeFormatting.DocumentOnTypeFormatting→CSharpLanguageServer.Runtime.RequestScheduling.RequestContext
- Direction
- CSharpLanguageServer.Handlers.DocumentOnTypeFormatting uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Handlers.DocumentOnTypeFormatting, while a change to CSharpLanguageServer.Handlers.DocumentOnTypeFormatting can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.DocumentOnTypeFormatting uses a module listed above it, which is the healthy direction.
24→3 CSharpLanguageServer.Handlers.DocumentRangeFormatting uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 5 pairs of types, where a type in CSharpLanguageServer.Handlers.DocumentRangeFormatting uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Handlers.DocumentRangeFormatting.DocumentRangeFormatting→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Handlers.DocumentRangeFormatting.DocumentRangeFormatting→Ionide.LanguageServerProtocol.Types.DocumentRangeFormattingOptionsCSharpLanguageServer.Handlers.DocumentRangeFormatting.DocumentRangeFormatting→Ionide.LanguageServerProtocol.Types.DocumentRangeFormattingParamsCSharpLanguageServer.Handlers.DocumentRangeFormatting.DocumentRangeFormatting→Ionide.LanguageServerProtocol.Types.RegistrationCSharpLanguageServer.Handlers.DocumentRangeFormatting.DocumentRangeFormatting→Ionide.LanguageServerProtocol.Types.U2`2
- Direction
- CSharpLanguageServer.Handlers.DocumentRangeFormatting uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Handlers.DocumentRangeFormatting, while a change to CSharpLanguageServer.Handlers.DocumentRangeFormatting can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.DocumentRangeFormatting uses a module listed above it, which is the healthy direction.
24→6 CSharpLanguageServer.Handlers.DocumentRangeFormatting uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.DocumentRangeFormatting uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Handlers.DocumentRangeFormatting.DocumentRangeFormatting→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Handlers.DocumentRangeFormatting uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Handlers.DocumentRangeFormatting, while a change to CSharpLanguageServer.Handlers.DocumentRangeFormatting can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.DocumentRangeFormatting uses a module listed above it, which is the healthy direction.
24→11 CSharpLanguageServer.Handlers.DocumentRangeFormatting uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.DocumentRangeFormatting uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Handlers.DocumentRangeFormatting.DocumentRangeFormatting→CSharpLanguageServer.Runtime.RequestScheduling.RequestContext
- Direction
- CSharpLanguageServer.Handlers.DocumentRangeFormatting uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Handlers.DocumentRangeFormatting, while a change to CSharpLanguageServer.Handlers.DocumentRangeFormatting can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.DocumentRangeFormatting uses a module listed above it, which is the healthy direction.
25→3 CSharpLanguageServer.Handlers.DocumentSymbol uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 7 pairs of types, where a type in CSharpLanguageServer.Handlers.DocumentSymbol uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Handlers.DocumentSymbol.DocumentSymbol→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Handlers.DocumentSymbol.DocumentSymbol→Ionide.LanguageServerProtocol.Types.DocumentSymbolCSharpLanguageServer.Handlers.DocumentSymbol.DocumentSymbol→Ionide.LanguageServerProtocol.Types.DocumentSymbolOptionsCSharpLanguageServer.Handlers.DocumentSymbol.DocumentSymbol→Ionide.LanguageServerProtocol.Types.DocumentSymbolParamsCSharpLanguageServer.Handlers.DocumentSymbol.DocumentSymbol→Ionide.LanguageServerProtocol.Types.RegistrationCSharpLanguageServer.Handlers.DocumentSymbol.DocumentSymbol→Ionide.LanguageServerProtocol.Types.U2`2CSharpLanguageServer.Handlers.DocumentSymbol.DocumentSymbolCollector→Ionide.LanguageServerProtocol.Types.DocumentSymbol
- Direction
- CSharpLanguageServer.Handlers.DocumentSymbol uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Handlers.DocumentSymbol, while a change to CSharpLanguageServer.Handlers.DocumentSymbol can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.DocumentSymbol uses a module listed above it, which is the healthy direction.
25→6 CSharpLanguageServer.Handlers.DocumentSymbol uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.DocumentSymbol uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Handlers.DocumentSymbol.DocumentSymbol→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Handlers.DocumentSymbol uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Handlers.DocumentSymbol, while a change to CSharpLanguageServer.Handlers.DocumentSymbol can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.DocumentSymbol uses a module listed above it, which is the healthy direction.
25→11 CSharpLanguageServer.Handlers.DocumentSymbol uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.DocumentSymbol uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Handlers.DocumentSymbol.DocumentSymbol→CSharpLanguageServer.Runtime.RequestScheduling.RequestContext
- Direction
- CSharpLanguageServer.Handlers.DocumentSymbol uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Handlers.DocumentSymbol, while a change to CSharpLanguageServer.Handlers.DocumentSymbol can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.DocumentSymbol uses a module listed above it, which is the healthy direction.
26→3 CSharpLanguageServer.Handlers.ExecuteCommand uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 4 pairs of types, where a type in CSharpLanguageServer.Handlers.ExecuteCommand uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Handlers.ExecuteCommand.ExecuteCommand→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Handlers.ExecuteCommand.ExecuteCommand→Ionide.LanguageServerProtocol.Types.ExecuteCommandOptionsCSharpLanguageServer.Handlers.ExecuteCommand.ExecuteCommand→Ionide.LanguageServerProtocol.Types.ExecuteCommandParamsCSharpLanguageServer.Handlers.ExecuteCommand.ExecuteCommand→Ionide.LanguageServerProtocol.Types.Registration
- Direction
- CSharpLanguageServer.Handlers.ExecuteCommand uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Handlers.ExecuteCommand, while a change to CSharpLanguageServer.Handlers.ExecuteCommand can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.ExecuteCommand uses a module listed above it, which is the healthy direction.
26→6 CSharpLanguageServer.Handlers.ExecuteCommand uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.ExecuteCommand uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Handlers.ExecuteCommand.ExecuteCommand→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Handlers.ExecuteCommand uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Handlers.ExecuteCommand, while a change to CSharpLanguageServer.Handlers.ExecuteCommand can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.ExecuteCommand uses a module listed above it, which is the healthy direction.
26→11 CSharpLanguageServer.Handlers.ExecuteCommand uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.ExecuteCommand uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Handlers.ExecuteCommand.ExecuteCommand→CSharpLanguageServer.Runtime.RequestScheduling.RequestContext
- Direction
- CSharpLanguageServer.Handlers.ExecuteCommand uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Handlers.ExecuteCommand, while a change to CSharpLanguageServer.Handlers.ExecuteCommand can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.ExecuteCommand uses a module listed above it, which is the healthy direction.
27→3 CSharpLanguageServer.Handlers.FoldingRange uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 8 pairs of types, where a type in CSharpLanguageServer.Handlers.FoldingRange uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Handlers.FoldingRange.FoldingRange→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Handlers.FoldingRange.FoldingRange→Ionide.LanguageServerProtocol.Types.FoldingRangeCSharpLanguageServer.Handlers.FoldingRange.FoldingRange→Ionide.LanguageServerProtocol.Types.FoldingRangeOptionsCSharpLanguageServer.Handlers.FoldingRange.FoldingRange→Ionide.LanguageServerProtocol.Types.FoldingRangeParamsCSharpLanguageServer.Handlers.FoldingRange.FoldingRange→Ionide.LanguageServerProtocol.Types.FoldingRangeRegistrationOptionsCSharpLanguageServer.Handlers.FoldingRange.FoldingRange→Ionide.LanguageServerProtocol.Types.RegistrationCSharpLanguageServer.Handlers.FoldingRange.FoldingRange→Ionide.LanguageServerProtocol.Types.U3`3CSharpLanguageServer.Handlers.FoldingRange.FoldingRangeCollector→Ionide.LanguageServerProtocol.Types.FoldingRange
- Direction
- CSharpLanguageServer.Handlers.FoldingRange uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Handlers.FoldingRange, while a change to CSharpLanguageServer.Handlers.FoldingRange can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.FoldingRange uses a module listed above it, which is the healthy direction.
27→6 CSharpLanguageServer.Handlers.FoldingRange uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.FoldingRange uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Handlers.FoldingRange.FoldingRange→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Handlers.FoldingRange uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Handlers.FoldingRange, while a change to CSharpLanguageServer.Handlers.FoldingRange can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.FoldingRange uses a module listed above it, which is the healthy direction.
27→11 CSharpLanguageServer.Handlers.FoldingRange uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.FoldingRange uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Handlers.FoldingRange.FoldingRange→CSharpLanguageServer.Runtime.RequestScheduling.RequestContext
- Direction
- CSharpLanguageServer.Handlers.FoldingRange uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Handlers.FoldingRange, while a change to CSharpLanguageServer.Handlers.FoldingRange can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.FoldingRange uses a module listed above it, which is the healthy direction.
28→3 CSharpLanguageServer.Handlers.Hover uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 6 pairs of types, where a type in CSharpLanguageServer.Handlers.Hover uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Handlers.Hover.Hover→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Handlers.Hover.Hover→Ionide.LanguageServerProtocol.Types.HoverCSharpLanguageServer.Handlers.Hover.Hover→Ionide.LanguageServerProtocol.Types.HoverOptionsCSharpLanguageServer.Handlers.Hover.Hover→Ionide.LanguageServerProtocol.Types.HoverParamsCSharpLanguageServer.Handlers.Hover.Hover→Ionide.LanguageServerProtocol.Types.RegistrationCSharpLanguageServer.Handlers.Hover.Hover→Ionide.LanguageServerProtocol.Types.U2`2
- Direction
- CSharpLanguageServer.Handlers.Hover uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Handlers.Hover, while a change to CSharpLanguageServer.Handlers.Hover can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Hover uses a module listed above it, which is the healthy direction.
28→6 CSharpLanguageServer.Handlers.Hover uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.Hover uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Handlers.Hover.Hover→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Handlers.Hover uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Handlers.Hover, while a change to CSharpLanguageServer.Handlers.Hover can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Hover uses a module listed above it, which is the healthy direction.
28→11 CSharpLanguageServer.Handlers.Hover uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.Hover uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Handlers.Hover.Hover→CSharpLanguageServer.Runtime.RequestScheduling.RequestContext
- Direction
- CSharpLanguageServer.Handlers.Hover uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Handlers.Hover, while a change to CSharpLanguageServer.Handlers.Hover can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Hover uses a module listed above it, which is the healthy direction.
29→3 CSharpLanguageServer.Handlers.Implementation uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 6 pairs of types, where a type in CSharpLanguageServer.Handlers.Implementation uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Handlers.Implementation.Implementation→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Handlers.Implementation.Implementation→Ionide.LanguageServerProtocol.Types.ImplementationOptionsCSharpLanguageServer.Handlers.Implementation.Implementation→Ionide.LanguageServerProtocol.Types.ImplementationParamsCSharpLanguageServer.Handlers.Implementation.Implementation→Ionide.LanguageServerProtocol.Types.ImplementationRegistrationOptionsCSharpLanguageServer.Handlers.Implementation.Implementation→Ionide.LanguageServerProtocol.Types.RegistrationCSharpLanguageServer.Handlers.Implementation.Implementation→Ionide.LanguageServerProtocol.Types.U3`3
- Direction
- CSharpLanguageServer.Handlers.Implementation uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Handlers.Implementation, while a change to CSharpLanguageServer.Handlers.Implementation can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Implementation uses a module listed above it, which is the healthy direction.
29→6 CSharpLanguageServer.Handlers.Implementation uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.Implementation uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Handlers.Implementation.Implementation→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Handlers.Implementation uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Handlers.Implementation, while a change to CSharpLanguageServer.Handlers.Implementation can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Implementation uses a module listed above it, which is the healthy direction.
29→9 CSharpLanguageServer.Handlers.Implementation uses CSharpLanguageServer.Lsp.WorkspaceFolder✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.Implementation uses a type in CSharpLanguageServer.Lsp.WorkspaceFolder.
- The types involved
CSharpLanguageServer.Handlers.Implementation.Implementation→CSharpLanguageServer.Lsp.WorkspaceFolder.LspWorkspaceFolder
- Direction
- CSharpLanguageServer.Handlers.Implementation uses CSharpLanguageServer.Lsp.WorkspaceFolder, so a change to CSharpLanguageServer.Lsp.WorkspaceFolder can break CSharpLanguageServer.Handlers.Implementation, while a change to CSharpLanguageServer.Handlers.Implementation can't break CSharpLanguageServer.Lsp.WorkspaceFolder.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Implementation uses a module listed above it, which is the healthy direction.
29→11 CSharpLanguageServer.Handlers.Implementation uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.Implementation uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Handlers.Implementation.Implementation→CSharpLanguageServer.Runtime.RequestScheduling.RequestContext
- Direction
- CSharpLanguageServer.Handlers.Implementation uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Handlers.Implementation, while a change to CSharpLanguageServer.Handlers.Implementation can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Implementation uses a module listed above it, which is the healthy direction.
30→3 CSharpLanguageServer.Handlers.InlayHint uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 7 pairs of types, where a type in CSharpLanguageServer.Handlers.InlayHint uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Handlers.InlayHint.InlayHint→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Handlers.InlayHint.InlayHint→Ionide.LanguageServerProtocol.Types.InlayHintCSharpLanguageServer.Handlers.InlayHint.InlayHint→Ionide.LanguageServerProtocol.Types.InlayHintOptionsCSharpLanguageServer.Handlers.InlayHint.InlayHint→Ionide.LanguageServerProtocol.Types.InlayHintParamsCSharpLanguageServer.Handlers.InlayHint.InlayHint→Ionide.LanguageServerProtocol.Types.InlayHintRegistrationOptionsCSharpLanguageServer.Handlers.InlayHint.InlayHint→Ionide.LanguageServerProtocol.Types.RegistrationCSharpLanguageServer.Handlers.InlayHint.InlayHint→Ionide.LanguageServerProtocol.Types.U3`3
- Direction
- CSharpLanguageServer.Handlers.InlayHint uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Handlers.InlayHint, while a change to CSharpLanguageServer.Handlers.InlayHint can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.InlayHint uses a module listed above it, which is the healthy direction.
30→6 CSharpLanguageServer.Handlers.InlayHint uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.InlayHint uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Handlers.InlayHint.InlayHint→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Handlers.InlayHint uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Handlers.InlayHint, while a change to CSharpLanguageServer.Handlers.InlayHint can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.InlayHint uses a module listed above it, which is the healthy direction.
30→11 CSharpLanguageServer.Handlers.InlayHint uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.InlayHint uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Handlers.InlayHint.InlayHint→CSharpLanguageServer.Runtime.RequestScheduling.RequestContext
- Direction
- CSharpLanguageServer.Handlers.InlayHint uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Handlers.InlayHint, while a change to CSharpLanguageServer.Handlers.InlayHint can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.InlayHint uses a module listed above it, which is the healthy direction.
31→3 CSharpLanguageServer.Handlers.InlineValue uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 4 pairs of types, where a type in CSharpLanguageServer.Handlers.InlineValue uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Handlers.InlineValue.InlineValue→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Handlers.InlineValue.InlineValue→Ionide.LanguageServerProtocol.Types.InlineValueOptionsCSharpLanguageServer.Handlers.InlineValue.InlineValue→Ionide.LanguageServerProtocol.Types.InlineValueParamsCSharpLanguageServer.Handlers.InlineValue.InlineValue→Ionide.LanguageServerProtocol.Types.Registration
- Direction
- CSharpLanguageServer.Handlers.InlineValue uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Handlers.InlineValue, while a change to CSharpLanguageServer.Handlers.InlineValue can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.InlineValue uses a module listed above it, which is the healthy direction.
31→6 CSharpLanguageServer.Handlers.InlineValue uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.InlineValue uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Handlers.InlineValue.InlineValue→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Handlers.InlineValue uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Handlers.InlineValue, while a change to CSharpLanguageServer.Handlers.InlineValue can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.InlineValue uses a module listed above it, which is the healthy direction.
31→11 CSharpLanguageServer.Handlers.InlineValue uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.InlineValue uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Handlers.InlineValue.InlineValue→CSharpLanguageServer.Runtime.RequestScheduling.RequestContext
- Direction
- CSharpLanguageServer.Handlers.InlineValue uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Handlers.InlineValue, while a change to CSharpLanguageServer.Handlers.InlineValue can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.InlineValue uses a module listed above it, which is the healthy direction.
32→3 CSharpLanguageServer.Handlers.LifeCycle uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.LifeCycle uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Handlers.LifeCycle.LifeCycle→Ionide.LanguageServerProtocol.Types.InitializeParams
- Direction
- CSharpLanguageServer.Handlers.LifeCycle uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Handlers.LifeCycle, while a change to CSharpLanguageServer.Handlers.LifeCycle can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.LifeCycle uses a module listed above it, which is the healthy direction.
32→5 CSharpLanguageServer.Handlers.LifeCycle uses Ionide.LanguageServerProtocol✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.LifeCycle uses a type in Ionide.LanguageServerProtocol.
- The types involved
CSharpLanguageServer.Handlers.LifeCycle.LifeCycle→Ionide.LanguageServerProtocol.ILspClient
- Direction
- CSharpLanguageServer.Handlers.LifeCycle uses Ionide.LanguageServerProtocol, so a change to Ionide.LanguageServerProtocol can break CSharpLanguageServer.Handlers.LifeCycle, while a change to CSharpLanguageServer.Handlers.LifeCycle can't break Ionide.LanguageServerProtocol.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.LifeCycle uses a module listed above it, which is the healthy direction.
32→11 CSharpLanguageServer.Handlers.LifeCycle uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.LifeCycle uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Handlers.LifeCycle.LifeCycle→CSharpLanguageServer.Runtime.RequestScheduling.RequestContext
- Direction
- CSharpLanguageServer.Handlers.LifeCycle uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Handlers.LifeCycle, while a change to CSharpLanguageServer.Handlers.LifeCycle can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.LifeCycle uses a module listed above it, which is the healthy direction.
33→3 CSharpLanguageServer.Handlers.Rename uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 7 pairs of types, where a type in CSharpLanguageServer.Handlers.Rename uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Handlers.Rename.Rename→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Handlers.Rename.Rename→Ionide.LanguageServerProtocol.Types.PrepareRenameParamsCSharpLanguageServer.Handlers.Rename.Rename→Ionide.LanguageServerProtocol.Types.RegistrationCSharpLanguageServer.Handlers.Rename.Rename→Ionide.LanguageServerProtocol.Types.RenameOptionsCSharpLanguageServer.Handlers.Rename.Rename→Ionide.LanguageServerProtocol.Types.RenameParamsCSharpLanguageServer.Handlers.Rename.Rename→Ionide.LanguageServerProtocol.Types.TextDocumentEditCSharpLanguageServer.Handlers.Rename.Rename→Ionide.LanguageServerProtocol.Types.U2`2
- Direction
- CSharpLanguageServer.Handlers.Rename uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Handlers.Rename, while a change to CSharpLanguageServer.Handlers.Rename can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Rename uses a module listed above it, which is the healthy direction.
33→6 CSharpLanguageServer.Handlers.Rename uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.Rename uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Handlers.Rename.Rename→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Handlers.Rename uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Handlers.Rename, while a change to CSharpLanguageServer.Handlers.Rename can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Rename uses a module listed above it, which is the healthy direction.
33→9 CSharpLanguageServer.Handlers.Rename uses CSharpLanguageServer.Lsp.WorkspaceFolder✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.Rename uses a type in CSharpLanguageServer.Lsp.WorkspaceFolder.
- The types involved
CSharpLanguageServer.Handlers.Rename.Rename→CSharpLanguageServer.Lsp.WorkspaceFolder.LspWorkspaceFolder
- Direction
- CSharpLanguageServer.Handlers.Rename uses CSharpLanguageServer.Lsp.WorkspaceFolder, so a change to CSharpLanguageServer.Lsp.WorkspaceFolder can break CSharpLanguageServer.Handlers.Rename, while a change to CSharpLanguageServer.Handlers.Rename can't break CSharpLanguageServer.Lsp.WorkspaceFolder.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Rename uses a module listed above it, which is the healthy direction.
33→11 CSharpLanguageServer.Handlers.Rename uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.Rename uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Handlers.Rename.Rename→CSharpLanguageServer.Runtime.RequestScheduling.RequestContext
- Direction
- CSharpLanguageServer.Handlers.Rename uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Handlers.Rename, while a change to CSharpLanguageServer.Handlers.Rename can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Rename uses a module listed above it, which is the healthy direction.
34→1 CSharpLanguageServer.Handlers.SemanticTokens uses Ionide.LanguageServerProtocol.JsonRpc✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.SemanticTokens uses a type in Ionide.LanguageServerProtocol.JsonRpc.
- The types involved
CSharpLanguageServer.Handlers.SemanticTokens.SemanticTokens→Ionide.LanguageServerProtocol.JsonRpc.Error
- Direction
- CSharpLanguageServer.Handlers.SemanticTokens uses Ionide.LanguageServerProtocol.JsonRpc, so a change to Ionide.LanguageServerProtocol.JsonRpc can break CSharpLanguageServer.Handlers.SemanticTokens, while a change to CSharpLanguageServer.Handlers.SemanticTokens can't break Ionide.LanguageServerProtocol.JsonRpc.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.SemanticTokens uses a module listed above it, which is the healthy direction.
34→3 CSharpLanguageServer.Handlers.SemanticTokens uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 10 pairs of types, where a type in CSharpLanguageServer.Handlers.SemanticTokens uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Handlers.SemanticTokens.SemanticTokens→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Handlers.SemanticTokens.SemanticTokens→Ionide.LanguageServerProtocol.Types.RangeCSharpLanguageServer.Handlers.SemanticTokens.SemanticTokens→Ionide.LanguageServerProtocol.Types.RegistrationCSharpLanguageServer.Handlers.SemanticTokens.SemanticTokens→Ionide.LanguageServerProtocol.Types.SemanticTokensCSharpLanguageServer.Handlers.SemanticTokens.SemanticTokens→Ionide.LanguageServerProtocol.Types.SemanticTokensDeltaParamsCSharpLanguageServer.Handlers.SemanticTokens.SemanticTokens→Ionide.LanguageServerProtocol.Types.SemanticTokensOptionsCSharpLanguageServer.Handlers.SemanticTokens.SemanticTokens→Ionide.LanguageServerProtocol.Types.SemanticTokensParamsCSharpLanguageServer.Handlers.SemanticTokens.SemanticTokens→Ionide.LanguageServerProtocol.Types.SemanticTokensRangeParamsCSharpLanguageServer.Handlers.SemanticTokens.SemanticTokens→Ionide.LanguageServerProtocol.Types.SemanticTokensRegistrationOptionsCSharpLanguageServer.Handlers.SemanticTokens.SemanticTokens→Ionide.LanguageServerProtocol.Types.U2`2
- Direction
- CSharpLanguageServer.Handlers.SemanticTokens uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Handlers.SemanticTokens, while a change to CSharpLanguageServer.Handlers.SemanticTokens can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.SemanticTokens uses a module listed above it, which is the healthy direction.
34→6 CSharpLanguageServer.Handlers.SemanticTokens uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.SemanticTokens uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Handlers.SemanticTokens.SemanticTokens→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Handlers.SemanticTokens uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Handlers.SemanticTokens, while a change to CSharpLanguageServer.Handlers.SemanticTokens can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.SemanticTokens uses a module listed above it, which is the healthy direction.
34→11 CSharpLanguageServer.Handlers.SemanticTokens uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.SemanticTokens uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Handlers.SemanticTokens.SemanticTokens→CSharpLanguageServer.Runtime.RequestScheduling.RequestContext
- Direction
- CSharpLanguageServer.Handlers.SemanticTokens uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Handlers.SemanticTokens, while a change to CSharpLanguageServer.Handlers.SemanticTokens can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.SemanticTokens uses a module listed above it, which is the healthy direction.
35→3 CSharpLanguageServer.Handlers.TextDocumentSync uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 11 pairs of types, where a type in CSharpLanguageServer.Handlers.TextDocumentSync uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Handlers.TextDocumentSync.TextDocumentSync→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Handlers.TextDocumentSync.TextDocumentSync→Ionide.LanguageServerProtocol.Types.DidChangeTextDocumentParamsCSharpLanguageServer.Handlers.TextDocumentSync.TextDocumentSync→Ionide.LanguageServerProtocol.Types.DidCloseTextDocumentParamsCSharpLanguageServer.Handlers.TextDocumentSync.TextDocumentSync→Ionide.LanguageServerProtocol.Types.DidOpenTextDocumentParamsCSharpLanguageServer.Handlers.TextDocumentSync.TextDocumentSync→Ionide.LanguageServerProtocol.Types.DidSaveTextDocumentParamsCSharpLanguageServer.Handlers.TextDocumentSync.TextDocumentSync→Ionide.LanguageServerProtocol.Types.RegistrationCSharpLanguageServer.Handlers.TextDocumentSync.TextDocumentSync→Ionide.LanguageServerProtocol.Types.TextDocumentContentChangeEventC1CSharpLanguageServer.Handlers.TextDocumentSync.TextDocumentSync→Ionide.LanguageServerProtocol.Types.TextDocumentContentChangeEventC2CSharpLanguageServer.Handlers.TextDocumentSync.TextDocumentSync→Ionide.LanguageServerProtocol.Types.TextDocumentSyncOptionsCSharpLanguageServer.Handlers.TextDocumentSync.TextDocumentSync→Ionide.LanguageServerProtocol.Types.U2`2CSharpLanguageServer.Handlers.TextDocumentSync.TextDocumentSync→Ionide.LanguageServerProtocol.Types.WillSaveTextDocumentParams
- Direction
- CSharpLanguageServer.Handlers.TextDocumentSync uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Handlers.TextDocumentSync, while a change to CSharpLanguageServer.Handlers.TextDocumentSync can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.TextDocumentSync uses a module listed above it, which is the healthy direction.
35→6 CSharpLanguageServer.Handlers.TextDocumentSync uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.TextDocumentSync uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Handlers.TextDocumentSync.TextDocumentSync→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Handlers.TextDocumentSync uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Handlers.TextDocumentSync, while a change to CSharpLanguageServer.Handlers.TextDocumentSync can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.TextDocumentSync uses a module listed above it, which is the healthy direction.
35→9 CSharpLanguageServer.Handlers.TextDocumentSync uses CSharpLanguageServer.Lsp.WorkspaceFolder✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.TextDocumentSync uses a type in CSharpLanguageServer.Lsp.WorkspaceFolder.
- The types involved
CSharpLanguageServer.Handlers.TextDocumentSync.TextDocumentSync→CSharpLanguageServer.Lsp.WorkspaceFolder.LspWorkspaceFolder
- Direction
- CSharpLanguageServer.Handlers.TextDocumentSync uses CSharpLanguageServer.Lsp.WorkspaceFolder, so a change to CSharpLanguageServer.Lsp.WorkspaceFolder can break CSharpLanguageServer.Handlers.TextDocumentSync, while a change to CSharpLanguageServer.Handlers.TextDocumentSync can't break CSharpLanguageServer.Lsp.WorkspaceFolder.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.TextDocumentSync uses a module listed above it, which is the healthy direction.
35→11 CSharpLanguageServer.Handlers.TextDocumentSync uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.TextDocumentSync uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Handlers.TextDocumentSync.TextDocumentSync→CSharpLanguageServer.Runtime.RequestScheduling.RequestContext
- Direction
- CSharpLanguageServer.Handlers.TextDocumentSync uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Handlers.TextDocumentSync, while a change to CSharpLanguageServer.Handlers.TextDocumentSync can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.TextDocumentSync uses a module listed above it, which is the healthy direction.
36→3 CSharpLanguageServer.Handlers.Workspace uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 6 pairs of types, where a type in CSharpLanguageServer.Handlers.Workspace uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Handlers.Workspace.Workspace→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Handlers.Workspace.Workspace→Ionide.LanguageServerProtocol.Types.DidChangeConfigurationParamsCSharpLanguageServer.Handlers.Workspace.Workspace→Ionide.LanguageServerProtocol.Types.DidChangeWatchedFilesParamsCSharpLanguageServer.Handlers.Workspace.Workspace→Ionide.LanguageServerProtocol.Types.DidChangeWorkspaceFoldersParamsCSharpLanguageServer.Handlers.Workspace.Workspace→Ionide.LanguageServerProtocol.Types.RegistrationCSharpLanguageServer.Handlers.Workspace.Workspace→Ionide.LanguageServerProtocol.Types.ServerCapabilitiesWorkspace
- Direction
- CSharpLanguageServer.Handlers.Workspace uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Handlers.Workspace, while a change to CSharpLanguageServer.Handlers.Workspace can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Workspace uses a module listed above it, which is the healthy direction.
36→6 CSharpLanguageServer.Handlers.Workspace uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.Workspace uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Handlers.Workspace.Workspace→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Handlers.Workspace uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Handlers.Workspace, while a change to CSharpLanguageServer.Handlers.Workspace can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Workspace uses a module listed above it, which is the healthy direction.
36→9 CSharpLanguageServer.Handlers.Workspace uses CSharpLanguageServer.Lsp.WorkspaceFolder✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.Workspace uses a type in CSharpLanguageServer.Lsp.WorkspaceFolder.
- The types involved
CSharpLanguageServer.Handlers.Workspace.Workspace→CSharpLanguageServer.Lsp.WorkspaceFolder.LspWorkspaceFolder
- Direction
- CSharpLanguageServer.Handlers.Workspace uses CSharpLanguageServer.Lsp.WorkspaceFolder, so a change to CSharpLanguageServer.Lsp.WorkspaceFolder can break CSharpLanguageServer.Handlers.Workspace, while a change to CSharpLanguageServer.Handlers.Workspace can't break CSharpLanguageServer.Lsp.WorkspaceFolder.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Workspace uses a module listed above it, which is the healthy direction.
36→11 CSharpLanguageServer.Handlers.Workspace uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Handlers.Workspace uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Handlers.Workspace.Workspace→CSharpLanguageServer.Runtime.RequestScheduling.RequestContext
- Direction
- CSharpLanguageServer.Handlers.Workspace uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Handlers.Workspace, while a change to CSharpLanguageServer.Handlers.Workspace can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Handlers.Workspace uses a module listed above it, which is the healthy direction.
37→6 CSharpLanguageServer.Runtime.DebugInfo uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Runtime.DebugInfo uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Runtime.DebugInfo.DebugInfo→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Runtime.DebugInfo uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Runtime.DebugInfo, while a change to CSharpLanguageServer.Runtime.DebugInfo can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Runtime.DebugInfo uses a module listed above it, which is the healthy direction.
37→9 CSharpLanguageServer.Runtime.DebugInfo uses CSharpLanguageServer.Lsp.WorkspaceFolder✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Runtime.DebugInfo uses a type in CSharpLanguageServer.Lsp.WorkspaceFolder.
- The types involved
CSharpLanguageServer.Runtime.DebugInfo.DebugInfo→CSharpLanguageServer.Lsp.WorkspaceFolder.LspWorkspaceFolder
- Direction
- CSharpLanguageServer.Runtime.DebugInfo uses CSharpLanguageServer.Lsp.WorkspaceFolder, so a change to CSharpLanguageServer.Lsp.WorkspaceFolder can break CSharpLanguageServer.Runtime.DebugInfo, while a change to CSharpLanguageServer.Runtime.DebugInfo can't break CSharpLanguageServer.Lsp.WorkspaceFolder.
- Position
- Below the diagonal: CSharpLanguageServer.Runtime.DebugInfo uses a module listed above it, which is the healthy direction.
37→10 CSharpLanguageServer.Runtime.DebugInfo uses CSharpLanguageServer.Lsp.Workspace✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Runtime.DebugInfo uses a type in CSharpLanguageServer.Lsp.Workspace.
- The types involved
CSharpLanguageServer.Runtime.DebugInfo.DebugInfo→CSharpLanguageServer.Lsp.Workspace.LspWorkspace
- Direction
- CSharpLanguageServer.Runtime.DebugInfo uses CSharpLanguageServer.Lsp.Workspace, so a change to CSharpLanguageServer.Lsp.Workspace can break CSharpLanguageServer.Runtime.DebugInfo, while a change to CSharpLanguageServer.Runtime.DebugInfo can't break CSharpLanguageServer.Lsp.Workspace.
- Position
- Below the diagonal: CSharpLanguageServer.Runtime.DebugInfo uses a module listed above it, which is the healthy direction.
37→11 CSharpLanguageServer.Runtime.DebugInfo uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 2 pairs of types, where a type in CSharpLanguageServer.Runtime.DebugInfo uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Runtime.DebugInfo.DebugInfo→CSharpLanguageServer.Runtime.RequestScheduling.RequestInfoCSharpLanguageServer.Runtime.DebugInfo.DebugInfo→CSharpLanguageServer.Runtime.RequestScheduling.RequestQueue
- Direction
- CSharpLanguageServer.Runtime.DebugInfo uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Runtime.DebugInfo, while a change to CSharpLanguageServer.Runtime.DebugInfo can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Runtime.DebugInfo uses a module listed above it, which is the healthy direction.
38→3 CSharpLanguageServer.Runtime.PushDiagnostics uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Runtime.PushDiagnostics uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Runtime.PushDiagnostics.PushDiagnostics→Ionide.LanguageServerProtocol.Types.ClientCapabilities
- Direction
- CSharpLanguageServer.Runtime.PushDiagnostics uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Runtime.PushDiagnostics, while a change to CSharpLanguageServer.Runtime.PushDiagnostics can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Runtime.PushDiagnostics uses a module listed above it, which is the healthy direction.
38→5 CSharpLanguageServer.Runtime.PushDiagnostics uses Ionide.LanguageServerProtocol✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Runtime.PushDiagnostics uses a type in Ionide.LanguageServerProtocol.
- The types involved
CSharpLanguageServer.Runtime.PushDiagnostics.PushDiagnostics→Ionide.LanguageServerProtocol.ILspClient
- Direction
- CSharpLanguageServer.Runtime.PushDiagnostics uses Ionide.LanguageServerProtocol, so a change to Ionide.LanguageServerProtocol can break CSharpLanguageServer.Runtime.PushDiagnostics, while a change to CSharpLanguageServer.Runtime.PushDiagnostics can't break Ionide.LanguageServerProtocol.
- Position
- Below the diagonal: CSharpLanguageServer.Runtime.PushDiagnostics uses a module listed above it, which is the healthy direction.
38→6 CSharpLanguageServer.Runtime.PushDiagnostics uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Runtime.PushDiagnostics uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Runtime.PushDiagnostics.PushDiagnostics→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Runtime.PushDiagnostics uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Runtime.PushDiagnostics, while a change to CSharpLanguageServer.Runtime.PushDiagnostics can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Runtime.PushDiagnostics uses a module listed above it, which is the healthy direction.
38→10 CSharpLanguageServer.Runtime.PushDiagnostics uses CSharpLanguageServer.Lsp.Workspace✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Runtime.PushDiagnostics uses a type in CSharpLanguageServer.Lsp.Workspace.
- The types involved
CSharpLanguageServer.Runtime.PushDiagnostics.PushDiagnostics→CSharpLanguageServer.Lsp.Workspace.LspWorkspace
- Direction
- CSharpLanguageServer.Runtime.PushDiagnostics uses CSharpLanguageServer.Lsp.Workspace, so a change to CSharpLanguageServer.Lsp.Workspace can break CSharpLanguageServer.Runtime.PushDiagnostics, while a change to CSharpLanguageServer.Runtime.PushDiagnostics can't break CSharpLanguageServer.Lsp.Workspace.
- Position
- Below the diagonal: CSharpLanguageServer.Runtime.PushDiagnostics uses a module listed above it, which is the healthy direction.
39→3 CSharpLanguageServer.Runtime.ServerStateLoop uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 5 pairs of types, where a type in CSharpLanguageServer.Runtime.ServerStateLoop uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Runtime.ServerStateLoop.PendingReconfiguration→Ionide.LanguageServerProtocol.Types.WorkspaceFolderCSharpLanguageServer.Runtime.ServerStateLoop.ServerEvent→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Runtime.ServerStateLoop.ServerEvent→Ionide.LanguageServerProtocol.Types.TraceValuesCSharpLanguageServer.Runtime.ServerStateLoop.ServerState→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Runtime.ServerStateLoop.ServerState→Ionide.LanguageServerProtocol.Types.TraceValues
- Direction
- CSharpLanguageServer.Runtime.ServerStateLoop uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Runtime.ServerStateLoop, while a change to CSharpLanguageServer.Runtime.ServerStateLoop can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Runtime.ServerStateLoop uses a module listed above it, which is the healthy direction.
39→5 CSharpLanguageServer.Runtime.ServerStateLoop uses Ionide.LanguageServerProtocol✕
- Connections
- 2 pairs of types, where a type in CSharpLanguageServer.Runtime.ServerStateLoop uses a type in Ionide.LanguageServerProtocol.
- The types involved
CSharpLanguageServer.Runtime.ServerStateLoop.ServerEvent→Ionide.LanguageServerProtocol.ILspClientCSharpLanguageServer.Runtime.ServerStateLoop.ServerState→Ionide.LanguageServerProtocol.ILspClient
- Direction
- CSharpLanguageServer.Runtime.ServerStateLoop uses Ionide.LanguageServerProtocol, so a change to Ionide.LanguageServerProtocol can break CSharpLanguageServer.Runtime.ServerStateLoop, while a change to CSharpLanguageServer.Runtime.ServerStateLoop can't break Ionide.LanguageServerProtocol.
- Position
- Below the diagonal: CSharpLanguageServer.Runtime.ServerStateLoop uses a module listed above it, which is the healthy direction.
39→6 CSharpLanguageServer.Runtime.ServerStateLoop uses CSharpLanguageServer.Types✕
- Connections
- 3 pairs of types, where a type in CSharpLanguageServer.Runtime.ServerStateLoop uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Runtime.ServerStateLoop.PendingReconfiguration→CSharpLanguageServer.Types.CSharpConfigurationCSharpLanguageServer.Runtime.ServerStateLoop.ServerEvent→CSharpLanguageServer.Types.CSharpConfigurationCSharpLanguageServer.Runtime.ServerStateLoop.ServerState→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Runtime.ServerStateLoop uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Runtime.ServerStateLoop, while a change to CSharpLanguageServer.Runtime.ServerStateLoop can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Runtime.ServerStateLoop uses a module listed above it, which is the healthy direction.
39→9 CSharpLanguageServer.Runtime.ServerStateLoop uses CSharpLanguageServer.Lsp.WorkspaceFolder✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Runtime.ServerStateLoop uses a type in CSharpLanguageServer.Lsp.WorkspaceFolder.
- The types involved
CSharpLanguageServer.Runtime.ServerStateLoop.ServerEvent→CSharpLanguageServer.Lsp.WorkspaceFolder.LspWorkspaceFolder
- Direction
- CSharpLanguageServer.Runtime.ServerStateLoop uses CSharpLanguageServer.Lsp.WorkspaceFolder, so a change to CSharpLanguageServer.Lsp.WorkspaceFolder can break CSharpLanguageServer.Runtime.ServerStateLoop, while a change to CSharpLanguageServer.Runtime.ServerStateLoop can't break CSharpLanguageServer.Lsp.WorkspaceFolder.
- Position
- Below the diagonal: CSharpLanguageServer.Runtime.ServerStateLoop uses a module listed above it, which is the healthy direction.
39→10 CSharpLanguageServer.Runtime.ServerStateLoop uses CSharpLanguageServer.Lsp.Workspace✕
- Connections
- 2 pairs of types, where a type in CSharpLanguageServer.Runtime.ServerStateLoop uses a type in CSharpLanguageServer.Lsp.Workspace.
- The types involved
CSharpLanguageServer.Runtime.ServerStateLoop.ServerEvent→CSharpLanguageServer.Lsp.Workspace.LspWorkspaceUpdateCSharpLanguageServer.Runtime.ServerStateLoop.ServerState→CSharpLanguageServer.Lsp.Workspace.LspWorkspace
- Direction
- CSharpLanguageServer.Runtime.ServerStateLoop uses CSharpLanguageServer.Lsp.Workspace, so a change to CSharpLanguageServer.Lsp.Workspace can break CSharpLanguageServer.Runtime.ServerStateLoop, while a change to CSharpLanguageServer.Runtime.ServerStateLoop can't break CSharpLanguageServer.Lsp.Workspace.
- Position
- Below the diagonal: CSharpLanguageServer.Runtime.ServerStateLoop uses a module listed above it, which is the healthy direction.
39→11 CSharpLanguageServer.Runtime.ServerStateLoop uses CSharpLanguageServer.Runtime.RequestScheduling✕
- Connections
- 5 pairs of types, where a type in CSharpLanguageServer.Runtime.ServerStateLoop uses a type in CSharpLanguageServer.Runtime.RequestScheduling.
- The types involved
CSharpLanguageServer.Runtime.ServerStateLoop.ServerEvent→CSharpLanguageServer.Runtime.RequestScheduling.RequestContextCSharpLanguageServer.Runtime.ServerStateLoop.ServerEvent→CSharpLanguageServer.Runtime.RequestScheduling.RequestModeCSharpLanguageServer.Runtime.ServerStateLoop.ServerState→CSharpLanguageServer.Runtime.RequestScheduling.RequestQueueCSharpLanguageServer.Runtime.ServerStateLoop.ServerStateLoop→CSharpLanguageServer.Runtime.RequestScheduling.RequestContextCSharpLanguageServer.Runtime.ServerStateLoop.ServerStateLoop→CSharpLanguageServer.Runtime.RequestScheduling.RequestMode
- Direction
- CSharpLanguageServer.Runtime.ServerStateLoop uses CSharpLanguageServer.Runtime.RequestScheduling, so a change to CSharpLanguageServer.Runtime.RequestScheduling can break CSharpLanguageServer.Runtime.ServerStateLoop, while a change to CSharpLanguageServer.Runtime.ServerStateLoop can't break CSharpLanguageServer.Runtime.RequestScheduling.
- Position
- Below the diagonal: CSharpLanguageServer.Runtime.ServerStateLoop uses a module listed above it, which is the healthy direction.
39→37 CSharpLanguageServer.Runtime.ServerStateLoop uses CSharpLanguageServer.Runtime.DebugInfo✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Runtime.ServerStateLoop uses a type in CSharpLanguageServer.Runtime.DebugInfo.
- The types involved
CSharpLanguageServer.Runtime.ServerStateLoop.ServerEvent→CSharpLanguageServer.Runtime.DebugInfo.DebugInfo
- Direction
- CSharpLanguageServer.Runtime.ServerStateLoop uses CSharpLanguageServer.Runtime.DebugInfo, so a change to CSharpLanguageServer.Runtime.DebugInfo can break CSharpLanguageServer.Runtime.ServerStateLoop, while a change to CSharpLanguageServer.Runtime.ServerStateLoop can't break CSharpLanguageServer.Runtime.DebugInfo.
- Position
- Below the diagonal: CSharpLanguageServer.Runtime.ServerStateLoop uses a module listed above it, which is the healthy direction.
39→38 CSharpLanguageServer.Runtime.ServerStateLoop uses CSharpLanguageServer.Runtime.PushDiagnostics✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Runtime.ServerStateLoop uses a type in CSharpLanguageServer.Runtime.PushDiagnostics.
- The types involved
CSharpLanguageServer.Runtime.ServerStateLoop.ServerState→CSharpLanguageServer.Runtime.PushDiagnostics.PushDiagnosticsState
- Direction
- CSharpLanguageServer.Runtime.ServerStateLoop uses CSharpLanguageServer.Runtime.PushDiagnostics, so a change to CSharpLanguageServer.Runtime.PushDiagnostics can break CSharpLanguageServer.Runtime.ServerStateLoop, while a change to CSharpLanguageServer.Runtime.ServerStateLoop can't break CSharpLanguageServer.Runtime.PushDiagnostics.
- Position
- Below the diagonal: CSharpLanguageServer.Runtime.ServerStateLoop uses a module listed above it, which is the healthy direction.
40→3 CSharpLanguageServer.Lsp.Server uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 4 pairs of types, where a type in CSharpLanguageServer.Lsp.Server uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
CSharpLanguageServer.Lsp.Server.Server→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesCSharpLanguageServer.Lsp.Server.Server→Ionide.LanguageServerProtocol.Types.InitializeParamsCSharpLanguageServer.Lsp.Server.Server→Ionide.LanguageServerProtocol.Types.RegistrationCSharpLanguageServer.Lsp.Server.Server→Ionide.LanguageServerProtocol.Types.ServerCapabilities
- Direction
- CSharpLanguageServer.Lsp.Server uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break CSharpLanguageServer.Lsp.Server, while a change to CSharpLanguageServer.Lsp.Server can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Lsp.Server uses a module listed above it, which is the healthy direction.
40→6 CSharpLanguageServer.Lsp.Server uses CSharpLanguageServer.Types✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Lsp.Server uses a type in CSharpLanguageServer.Types.
- The types involved
CSharpLanguageServer.Lsp.Server.Server→CSharpLanguageServer.Types.CSharpConfiguration
- Direction
- CSharpLanguageServer.Lsp.Server uses CSharpLanguageServer.Types, so a change to CSharpLanguageServer.Types can break CSharpLanguageServer.Lsp.Server, while a change to CSharpLanguageServer.Lsp.Server can't break CSharpLanguageServer.Types.
- Position
- Below the diagonal: CSharpLanguageServer.Lsp.Server uses a module listed above it, which is the healthy direction.
40→39 CSharpLanguageServer.Lsp.Server uses CSharpLanguageServer.Runtime.ServerStateLoop✕
- Connections
- 1 pair of types, where a type in CSharpLanguageServer.Lsp.Server uses a type in CSharpLanguageServer.Runtime.ServerStateLoop.
- The types involved
CSharpLanguageServer.Lsp.Server.Server→CSharpLanguageServer.Runtime.ServerStateLoop.ServerEvent
- Direction
- CSharpLanguageServer.Lsp.Server uses CSharpLanguageServer.Runtime.ServerStateLoop, so a change to CSharpLanguageServer.Runtime.ServerStateLoop can break CSharpLanguageServer.Lsp.Server, while a change to CSharpLanguageServer.Lsp.Server can't break CSharpLanguageServer.Runtime.ServerStateLoop.
- Position
- Below the diagonal: CSharpLanguageServer.Lsp.Server uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 8 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 7 | Medium |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with CSharpLanguageServer.fsproj; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Reconcile the README with reality: src/CSharpLanguageServer/README.md links to `docs/features.md`, but `src/CSharpLanguageServer/docs/features.md` does not exist; src/CSharpLanguageServer/README.md links to `docs/troubleshooting.md`, but `src/CSharpLanguageServer/docs/troubleshooting.md` does not exist; src/CSharpLanguageServer/README.md links to `CONTRIBUTING.md`, but `src/CSharpLanguageServer/CONTRIBUTING.md` does not exist; src/CSharpLanguageServer/README.md links to `docs/codebase-architecture.md`, but `src/CSharpLanguageServer/docs/codebase-architecture.md` does not exist.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with CSharpLanguageServer.fsproj. | +8.7 pts | Low | ADR Quality |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +7.1 pts | Medium | Architecture documentation |
| Reconcile the README with reality: src/CSharpLanguageServer/README.md links to `docs/features.md`, but `src/CSharpLanguageServer/docs/features.md` does not exist; src/CSharpLanguageServer/README.md links to `docs/troubleshooting.md`, but `src/CSharpLanguageServer/docs/troubleshooting.md` does not exist; src/CSharpLanguageServer/README.md links to `CONTRIBUTING.md`, but `src/CSharpLanguageServer/CONTRIBUTING.md` does not exist; src/CSharpLanguageServer/README.md links to `docs/codebase-architecture.md`, but `src/CSharpLanguageServer/docs/codebase-architecture.md` does not exist. | +7.1 pts | Medium | Documentation accuracy |
| Resolve the 2 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Packages.props (2). | +1.5 pts | Low | Explicit Debt |
| Resolve the 1 Scattered collaborators finding(s) in Navigability. | +1.1 pts | Low | Navigability |
| Resolve the 1 Outdated finding(s) in Dependency Hygiene — start with Directory.Packages.props. | +0.6 pts | Low | Dependency Hygiene |
| The .NET analyzers are running but not blocking — tighten them (set <AnalysisMode>All</AnalysisMode>, or treat analyzer warnings as errors on CI) so a security/quality regression fails the build rather than scrolling past as a warning. | +1.1 pts | Medium | Security & performance tooling |
| Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production. | +0.7 pts | Medium | Observability |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| Directory.Packages.props | 5.9 | Mixed | Explicit Debt: NoWarnInCsproj — known-vulnerability alert suppressed |
| src/Ionide.LanguageServerProtocol/tools/MetaModelGenerator/GenerateTypes.fs | 7.0 | Near-clean | Cyclomatic Complexity: GenerateTypes.createField (cyclomatic 20) |
| src/CSharpLanguageServer/Handlers/CallHierarchy.fs | 7.1 | Near-clean | Cyclomatic Complexity: CallHierarchy.outgoingCalls (cyclomatic 20) |
| src/Ionide.LanguageServerProtocol/src/Types.cg.fs | 7.1 | Near-clean | God Classes: FileTooLong: src/Types.cg.fs |
| src/Ionide.LanguageServerProtocol/src/JsonUtils.fs | 7.2 | Near-clean | Cyclomatic Complexity: ErasedUnionConverter`1.Read (cyclomatic 33) |
| src/CSharpLanguageServer/Handlers/InlayHint.fs | 7.4 | Near-clean | Cyclomatic Complexity: InlayHint.toInlayHint (cyclomatic 57) |
| src/CSharpLanguageServer/Runtime/JsonRpc.fs | 7.4 | Near-clean | Cyclomatic Complexity: JsonRpc.processEvent (cyclomatic 40) |
| src/Ionide.LanguageServerProtocol/tools/MetaModelGenerator/GenerateClientServer.fs | 7.4 | Near-clean | Cyclomatic Complexity: GenerateClientServer.generateClientServer (cyclomatic 33) |
| src/CSharpLanguageServer/Roslyn/Conversions.fs | 7.4 | Near-clean | Cyclomatic Complexity: SymbolKind.fromSymbol (cyclomatic 23) |
| src/CSharpLanguageServer/Handlers/DocumentSync.fs | 7.4 | Near-clean | Code Duplication: Duplicated block (7–9 lines × 2) |
| src/CSharpLanguageServer/Runtime/ServerStateLoop.fs | 7.8 | Near-clean | Cyclomatic Complexity: ServerStateLoop.processServerEvent (cyclomatic 72) |
| src/CSharpLanguageServer/Runtime/PushDiagnostics.fs | 7.8 | Near-clean | Cyclomatic Complexity: PushDiagnostics.processPendingPushDiagnostics (cyclomatic 18) |
| src/CSharpLanguageServer/Lsp/WorkspaceFolder.fs | 7.8 | Near-clean | Cyclomatic Complexity: WorkspaceFolder.workspaceFolderDocumentDetails (cyclomatic 16) |
| src/CSharpLanguageServer/Handlers/CodeAction.fs | 7.8 | Near-clean | Cognitive Complexity: CodeAction.getRoslynCodeActions (cognitive 18) |
| src/CSharpLanguageServer/Handlers/DocumentOnTypeFormatting.fs | 7.8 | Near-clean | Cognitive Complexity: DocumentOnTypeFormatting.getSyntaxNode (cognitive 16) |
| src/CSharpLanguageServer/Handlers/DocumentSymbol.fs | 7.8 | Near-clean | Code Duplication: Duplicated block (10 lines × 2) |
| src/CSharpLanguageServer/Program.fs | 8.5 | Near-clean | Cyclomatic Complexity: Program.entry (cyclomatic 18) |
| src/CSharpLanguageServer/Handlers/Diagnostic.fs | 8.5 | Near-clean | Cognitive Complexity: Diagnostic.getWorkspaceDiagnosticReports (cognitive 26) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 38 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 38 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 94 of 118 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
- D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A hotspot's complexity is meant to be the worst body its churn actually touched. For src/CSharpLanguageServer/Runtime/ServerStateLoop.fs, src/CSharpLanguageServer/Lsp/WorkspaceFolder.fs, src/CSharpLanguageServer/Handlers/CallHierarchy.fs, src/Ionide.LanguageServerProtocol/src/JsonUtils.fs that could not be established — the complexity reader for the file reports no body extents, or the history carries no per-line attribution — so the row quotes the file's worst body, which the counted changes may never have touched. The churn count is unaffected.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (24 contributor(s) across 1356 commit(s) sampled, automation and bot accounts excluded). One of them holds 90% of the history; the other 23 hold 0.4% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'src/CSharpLanguageServer/CSharpLanguageServer.fsproj' because the file extension '.fsproj' is not associated with a language.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 2 deducted marker(s) and the 2.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (22,225 lines, 100% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X14 Bypassable address classification — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X26 Unsynchronised callback handoff — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X32 Type resolved by simple name across every loaded assembly — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
13 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ServerStateLoop.processServerEvent at 72. A further 3 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Completion.roslynTagToLspCompletion at 21 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/CSharpLanguageServer/DocumentationUtil.fs (DocumentationUtil.formatTextElement at 21), src/CSharpLanguageServer/Handlers/Completion.fs (Completion.roslynTagToLspCompletion at 21), src/CSharpLanguageServer/Handlers/DocumentSymbol.fs (DocumentSymbol.getSymbolNameAndKind at 20). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 13 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with ServerStateLoop.processServerEvent (cyclomatic 72), InlayHint.toInlayHint (cyclomatic 57), JsonRpc.processEvent (cyclomatic 40). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 13 together lifts Cyclomatic Complexity from 7.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
17 method(s) exceeded the cognitive complexity threshold of 15; the worst was ServerStateLoop.processServerEvent at 60.
What to do
- Bring the 17 bodies over 15 down to 15 or less in Cognitive Complexity — start with ServerStateLoop.processServerEvent (cognitive 60), ErasedUnionConverter`1.Read (cognitive 56), InlayHint.toInlayHint (cognitive 50). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 17 together lifts Cognitive Complexity from 7.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
6 god class(es) detected.
What to do
- Resolve the 4 FileTooLong finding(s) in God Classes — start with Types.cg.fs, JsonRpc.fs, GenerateTypes.fs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with Server.fs, Client.fs. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
28 duplicated block group(s) detected. A further 3 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 5 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with CodeAction.fs, DocumentOnTypeFormatting.fs, SignatureHelp.fs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 Duplicated block (10 lines × 3) finding(s) in Code Duplication — start with InlayHint.fs, DocumentSync.fs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with DocumentSync.fs, FsLibLog.fs. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
33 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 12 classes have LCOM4 above 3.
D12 · Dependency Hygiene
16 outdated, 0 vulnerable, 0 deprecated packages.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 11 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 22 direct `PackageReference`(s), and 10 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
Top hotspots: src/CSharpLanguageServer/Runtime/ServerStateLoop.fs (3×72=216); src/CSharpLanguageServer/Handlers/CallHierarchy.fs (5×20=100); src/Ionide.LanguageServerProtocol/src/JsonUtils.fs (2×33=66) Repeated repair below the complexity floor: src/CSharpLanguageServer/Roslyn/Solution.fs (4 of 5 changes were fixes)
What to do
- Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with ServerStateLoop.fs, CallHierarchy.fs, JsonUtils.fs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with Solution.fs. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
2 deducted debt markers + unmeasured dead symbols across 0 LoC in the .NET projects (2.0/KLoC) → score 6.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (100% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
What to do
- Resolve the 2 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Packages.props (2). — One of this dimension's main actionable groups (2 issue-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 7 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with CSharpLanguageServer.fsproj. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 31 projects flagged as possibly oversized/incoherent.
D27 · Navigability
94 % of calls cross a namespace and 2 % go through an interface, but 57 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
8 finding(s): 0 critical, 8 high, 0 medium, 0 low. 8 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- No action in Static Analysis (SAST) — all 8 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (8 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 62 of the 75 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: Implementation.fs↔TypeDefinition.fs 50%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with Implementation.fs. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 35 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- src/CSharpLanguageServer/README.md links to `docs/features.md`, but `src/CSharpLanguageServer/docs/features.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/CSharpLanguageServer/README.md:26
- src/CSharpLanguageServer/README.md links to `docs/troubleshooting.md`, but `src/CSharpLanguageServer/docs/troubleshooting.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/CSharpLanguageServer/README.md:29
- src/CSharpLanguageServer/README.md links to `CONTRIBUTING.md`, but `src/CSharpLanguageServer/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/CSharpLanguageServer/README.md:32
- src/CSharpLanguageServer/README.md links to `docs/codebase-architecture.md`, but `src/CSharpLanguageServer/docs/codebase-architecture.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/CSharpLanguageServer/README.md:34
What to do
- Reconcile the README with reality: src/CSharpLanguageServer/README.md links to `docs/features.md`, but `src/CSharpLanguageServer/docs/features.md` does not exist; src/CSharpLanguageServer/README.md links to `docs/troubleshooting.md`, but `src/CSharpLanguageServer/docs/troubleshooting.md` does not exist; src/CSharpLanguageServer/README.md links to `CONTRIBUTING.md`, but `src/CSharpLanguageServer/CONTRIBUTING.md` does not exist; src/CSharpLanguageServer/README.md links to `docs/codebase-architecture.md`, but `src/CSharpLanguageServer/docs/codebase-architecture.md` does not exist.
P1 · CI/CD gates
P2 · Observability
- Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `src/Ionide.LanguageServerProtocol/tools/MetaModelGenerator`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add a health-check endpoint (ASP.NET Core's MapHealthChecks, or a /health route in your Giraffe/Suave app) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- <NuGetAudit>false</NuGetAudit> in MSBuild suppresses NuGet's vulnerability audit project-wide. — tests/CSharpLanguageServer.Tests/Fixtures/platformSpecificTfm/Project/Project.csproj:6
- `NoWarn` silences NU1902, NU1903 — NuGet's vulnerability-audit warnings for moderate and high advisories. Suppressed advisories are still shipped; they are only invisible in the build log. Remove these codes from NoWarn and address or explicitly accept each advisory instead. — Directory.Packages.props:11
- `Directory.Packages.props` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — Directory.Packages.props:14
What to do
- The .NET analyzers are running but not blocking — tighten them (set <AnalysisMode>All</AnalysisMode>, or treat analyzer warnings as errors on CI) so a security/quality regression fails the build rather than scrolling past as a warning.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
PF3 · Async & latency hygiene
X23 · Unguarded diagnostic materialisation
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 69% | Strong | Solid. |
| Architecture | 62% | Adequate — gated by AX10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 50% | Adequate — gated by M2, M4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 68% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 75% | Checked 4 of 10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 72 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's F# imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No F# function in this code takes an ASP.NET Core or Suave HttpContext (a Giraffe, Saturn, Falco, Oxpecker or Suave handler) and no F# class is an ASP.NET Core controller, so no request handler shares module state between request threads.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~11413 lines of test source are present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not measured — no test run produced results
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F# not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — single shared-core project — no cross-context coupling to assess
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: this repository did not build in our analyzer environment (a C#/MSBuild compiler error), so no coverage could be collected. It is excluded from the score rather than counted as a near-zero defect. We did not read WHERE the failing diagnostic is, so this does not claim the fault is in your test code — a repository written for an older SDK band can compile for you and not for us. Run `dotnet build` on this commit; if it succeeds, the gap is ours. Committing the Cobertura/OpenCover/lcov report your CI already produces also lets us measure real coverage without building anything.
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 414 value object(s); 6 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — reported, not scored — this repository's C# declares no analysable method bodies (a constants, record or DTO assembly), and this score is a density of unfinished work per method, which has no denominator here. The file-level signals below were still collected and are shown in full
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 12 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- NoWarnInCsproj — known-vulnerability alert suppressed Directory.Packages.props:11
- NoWarnInCsproj — known-vulnerability alert suppressed Directory.Packages.props:11
- NuGet vulnerability audit disabled (csproj) tests/CSharpLanguageServer.Tests/Fixtures/platformSpecificTfm/Project/Project.csproj:6
- NuGet vulnerability audit suppressed via NoWarn Directory.Packages.props:11
Serious — 77 finding(s)
- Duplicated block (11 lines × 2) src/CSharpLanguageServer/Handlers/CodeAction.fs:255
- Duplicated block (11 lines × 2) src/CSharpLanguageServer/Handlers/DocumentOnTypeFormatting.fs:77
- Duplicated block (11 lines × 2) src/CSharpLanguageServer/Handlers/SignatureHelp.fs:132
- Duplicated block (11 lines × 2) src/Ionide.LanguageServerProtocol/tools/MetaModelGenerator/GenerateClientServer.fs:111
- Duplicated block (11 lines × 2) src/Ionide.LanguageServerProtocol/tools/MetaModelGenerator/GenerateTypes.fs:49
- Hotspot: src/CSharpLanguageServer/Runtime/ServerStateLoop.fs src/CSharpLanguageServer/Runtime/ServerStateLoop.fs:115
- Hotspot: src/CSharpLanguageServer/Handlers/CallHierarchy.fs src/CSharpLanguageServer/Handlers/CallHierarchy.fs:134
- Hotspot: src/Ionide.LanguageServerProtocol/src/JsonUtils.fs src/Ionide.LanguageServerProtocol/src/JsonUtils.fs:428
- Hotspot: src/CSharpLanguageServer/Lsp/WorkspaceFolder.fs src/CSharpLanguageServer/Lsp/WorkspaceFolder.fs:447
- FileTooLong: src/Types.cg.fs src/Ionide.LanguageServerProtocol/src/Types.cg.fs
- FileTooLong: Runtime/JsonRpc.fs src/CSharpLanguageServer/Runtime/JsonRpc.fs
- FileTooLong: MetaModelGenerator/GenerateTypes.fs src/Ionide.LanguageServerProtocol/tools/MetaModelGenerator/GenerateTypes.fs
- FileTooLong: Lsp/WorkspaceFolder.fs src/CSharpLanguageServer/Lsp/WorkspaceFolder.fs
- TooManyMethods: LspServer src/Ionide.LanguageServerProtocol/src/Server.fs:16
- TooManyMethods: LspClient src/Ionide.LanguageServerProtocol/src/Client.fs:16
- REDACTED
- REDACTED
- Duplicated block (10 lines × 3) src/CSharpLanguageServer/Handlers/InlayHint.fs:703
- Duplicated block (10 lines × 3) src/CSharpLanguageServer/Handlers/DocumentSync.fs:67
- Duplicated block (9 lines × 2) src/CSharpLanguageServer/Handlers/DocumentSync.fs:62
- Duplicated block (9 lines × 2) src/Ionide.LanguageServerProtocol/src/FsLibLog.fs:449
- ServerStateLoop.processServerEvent (cyclomatic 72) src/CSharpLanguageServer/Runtime/ServerStateLoop.fs:115
- InlayHint.toInlayHint (cyclomatic 57) src/CSharpLanguageServer/Handlers/InlayHint.fs:238
- JsonRpc.processEvent (cyclomatic 40) src/CSharpLanguageServer/Runtime/JsonRpc.fs:674
- ErasedUnionConverter`1.Read (cyclomatic 33) src/Ionide.LanguageServerProtocol/src/JsonUtils.fs:428
- GenerateClientServer.generateClientServer (cyclomatic 33) src/Ionide.LanguageServerProtocol/tools/MetaModelGenerator/GenerateClientServer.fs:13
- SymbolKind.fromSymbol (cyclomatic 23) src/CSharpLanguageServer/Roslyn/Conversions.fs:85
- CallHierarchy.outgoingCalls (cyclomatic 20) src/CSharpLanguageServer/Handlers/CallHierarchy.fs:134
- GenerateTypes.createField (cyclomatic 20) src/Ionide.LanguageServerProtocol/tools/MetaModelGenerator/GenerateTypes.fs:181
- GenerateTypes.createStructure (cyclomatic 20) src/Ionide.LanguageServerProtocol/tools/MetaModelGenerator/GenerateTypes.fs:461
- GenerateTypes.createTypeAlias (cyclomatic 20) src/Ionide.LanguageServerProtocol/tools/MetaModelGenerator/GenerateTypes.fs:652
- Program.entry (cyclomatic 18) src/CSharpLanguageServer/Program.fs:52
- PushDiagnostics.processPendingPushDiagnostics (cyclomatic 18) src/CSharpLanguageServer/Runtime/PushDiagnostics.fs:41
- WorkspaceFolder.workspaceFolderDocumentDetails (cyclomatic 16) src/CSharpLanguageServer/Lsp/WorkspaceFolder.fs:447
- Repeated repair: src/CSharpLanguageServer/Roslyn/Solution.fs src/CSharpLanguageServer/Roslyn/Solution.fs:506
- ServerStateLoop.processServerEvent (cognitive 60) src/CSharpLanguageServer/Runtime/ServerStateLoop.fs:115
- ErasedUnionConverter`1.Read (cognitive 56) src/Ionide.LanguageServerProtocol/src/JsonUtils.fs:428
- InlayHint.toInlayHint (cognitive 50) src/CSharpLanguageServer/Handlers/InlayHint.fs:238
- CallHierarchy.outgoingCalls (cognitive 50) src/CSharpLanguageServer/Handlers/CallHierarchy.fs:134
- GenerateClientServer.generateClientServer (cognitive 48) src/Ionide.LanguageServerProtocol/tools/MetaModelGenerator/GenerateClientServer.fs:13
- JsonRpc.processEvent (cognitive 37) src/CSharpLanguageServer/Runtime/JsonRpc.fs:674
- PushDiagnostics.processPendingPushDiagnostics (cognitive 33) src/CSharpLanguageServer/Runtime/PushDiagnostics.fs:41
- GenerateTypes.createStructure (cognitive 32) src/Ionide.LanguageServerProtocol/tools/MetaModelGenerator/GenerateTypes.fs:461
- Diagnostic.getWorkspaceDiagnosticReports (cognitive 26) src/CSharpLanguageServer/Handlers/Diagnostic.fs:139
- Completion.getCompletionsForRazorDocument (cognitive 24) src/CSharpLanguageServer/Handlers/Completion.fs:239
- GenerateTypes.createTypeAlias (cognitive 24) src/Ionide.LanguageServerProtocol/tools/MetaModelGenerator/GenerateTypes.fs:652
- GenerateTypes.createField (cognitive 23) src/Ionide.LanguageServerProtocol/tools/MetaModelGenerator/GenerateTypes.fs:181
- Document.normalizeDocumentEndOfFile (cognitive 22) src/CSharpLanguageServer/Roslyn/Document.fs:94
- LspTraceLogger.Microsoft.Extensions.Logging.ILogger.Log (cognitive 19) src/CSharpLanguageServer/Logging.fs:30
- CodeAction.getRoslynCodeActions (cognitive 18) src/CSharpLanguageServer/Handlers/CodeAction.fs:78
- CSharpMetadata.handle (cognitive 17) src/CSharpLanguageServer/Handlers/CSharpMetadata.fs:13
- DocumentOnTypeFormatting.getSyntaxNode (cognitive 16) src/CSharpLanguageServer/Handlers/DocumentOnTypeFormatting.fs:50
- Change coupling: Implementation.fs ↔ TypeDefinition.fs src/CSharpLanguageServer/Handlers/Implementation.fs:1
- REDACTED
- Members sharing a duplicated core (7 members, 50+ identical tokens) src/CSharpLanguageServer/Handlers/CallHierarchy.fs:1
- Edited copy of a member (23 corresponding lines) src/CSharpLanguageServer/Handlers/Color.fs:1
- Edited copies of one member (6 members, 20+ corresponding lines) src/CSharpLanguageServer/Handlers/Declaration.fs:1
- Duplicated block (43 lines × 2) src/Ionide.LanguageServerProtocol/src/Types.cg.fs:1738
- Duplicated block (24–33 lines × 2) src/Ionide.LanguageServerProtocol/src/Types.cg.fs:2241
- Duplicated block (24 lines × 6) src/Ionide.LanguageServerProtocol/src/Types.cg.fs:401
- Duplicated block (16 lines × 7) src/Ionide.LanguageServerProtocol/src/Types.cg.fs:409
- Duplicated block (15 lines × 2) src/CSharpLanguageServer/Roslyn/Conversions.fs:139
- Duplicated block (14 lines × 2) src/CSharpLanguageServer/Handlers/CallHierarchy.fs:57
- Duplicated block (11–13 lines × 2) src/CSharpLanguageServer/Handlers/TypeHierarchy.fs:105
- Duplicated block (13 lines × 2) src/Ionide.LanguageServerProtocol/src/JsonUtils.fs:538
- Duplicated block (12 lines × 2) src/CSharpLanguageServer/Roslyn/Conversions.fs:124
- Duplicated block (9–10 lines × 2) src/CSharpLanguageServer/Handlers/CallHierarchy.fs:138
- Duplicated block (10 lines × 2) src/CSharpLanguageServer/Handlers/DocumentSymbol.fs:325
- Duplicated block (9 lines × 7) src/CSharpLanguageServer/Handlers/CallHierarchy.fs:56
- Duplicated block (7–9 lines × 4) src/CSharpLanguageServer/Handlers/DocumentRangeFormatting.fs:53
- Duplicated block (7–9 lines × 3) src/CSharpLanguageServer/Handlers/CodeLens.fs:125
- Duplicated block (8–9 lines × 2) src/CSharpLanguageServer/Handlers/DocumentSymbol.fs:55
- Duplicated block (7–9 lines × 2) src/CSharpLanguageServer/Handlers/DocumentSync.fs:182
- Duplicated block (8 lines × 3) src/CSharpLanguageServer/Handlers/DocumentFormatting.fs:55
- Duplicated block (8 lines × 2) src/Ionide.LanguageServerProtocol/src/JsonUtils.fs:328
- Duplicated block (7 lines × 2) src/CSharpLanguageServer/Handlers/Workspace.fs:161
- Coverage not measured — test suite did not build
Minor — 14 finding(s)
- README/code drift src/CSharpLanguageServer/README.md:26
- README/code drift src/CSharpLanguageServer/README.md:29
- README/code drift src/CSharpLanguageServer/README.md:32
- README/code drift src/CSharpLanguageServer/README.md:34
- Outdated: coverlet.collector Directory.Packages.props:20
- No ADRs found src/CSharpLanguageServer/CSharpLanguageServer.fsproj:5
- Scattered collaborators
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Logging is not universal
- No dependency-update automation Directory.Packages.props:14
Minor — 15 finding(s)
- Outdated: DotNet.ReproducibleBuilds
- Outdated: FSharp.Control.AsyncSeq
- Outdated: ICSharpCode.Decompiler
- Outdated: Ionide.KeepAChangelog.Tasks
- Outdated: Microsoft.Build
- Outdated: Microsoft.Build.Framework
- Outdated: Microsoft.Build.Locator
- Outdated: Microsoft.Extensions.Caching.Memory
- Outdated: Microsoft.Extensions.Logging
- Outdated: Microsoft.Extensions.Logging.Console
- Outdated: NuGet.Frameworks
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: NUnit
- Outdated: NUnit3TestAdapter
- Outdated: System.Text.Json
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-0650350336c54011a93fe8a2d00efec8/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-0650350336c54011a93fe8a2d00efec8/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 8 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list csharp-language-server.sln package --vulnerable --include-transitive --format json | 0 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-d905afe9fa024cb1abd8873a297b3b7c | 0 | artifacts/raw/osv-scanner.json |