Table of Contents

Namespace RDCore.SDK.Extensibility.Diagnostics

Classes

AnalyzerFinding

One thing an analyzer has to say about a module.

DiagnoseDocumentParams

Request for rdcore/diagnostics/document: the language server hands a diagnostics-provider extension everything it needs to analyze one document and asks for the diagnostics it finds.

DiagnoseDocumentPayload

The System.Text.Json payload carried in Json.

DiagnoseDocumentResult

Response to rdcore/diagnostics/document: the diagnostics a provider found, already projected to LSP Diagnostics (code, codeDescription help URL, and structured data), plus the source version echoed back for the language server's staleness gate.

DiagnosticFixes

What can be done about a finding, which the platform knows how to do: the fixes an analyzer states with what it found, and which travel with the diagnostic in its data (LSP 3.17 Diagnostic.data) for the language server to offer as code actions.

EditFix

Edits of the document a finding is in, which fix it: what the code action that makes them is called, and the edits, of the version of the document the finding was made of.

LineEdits

The edits of a fix (EditFix) that remove or write whole lines, placed by the parse of the module an analyzer is given (ParseResult): which lines a node is alone on, and lines of their own written before or after one.

ModuleAnalysisContext

What an analyzer is given of a module: the syntax tree, and the facts the platform's semantic analysis pass found out about it.

ModuleAnalyzerHost

Runs the analyzers of an extension over a document, as the platform runs them for every extension: those of the phase asked for, and only those that report a code that is not disabled for the document.

ProjectChange

One change of the project, which a ProjectFix makes: a library the project is to reference, or what it is to say of the module a finding is in.

ProjectFix

A change of the project that fixes a finding: what the project file (ProjectFile) is to say of the module the finding is in, or of the libraries the project references, which the language server writes in the project file of the workspace when the fix is taken.

ProjectFixText

Why a change of the project that fixes a finding (ProjectChange) is not made, in the language of the reader, the current UI culture by default: what a language server answers a client whose project changed since the fix was offered.

RefactoringFix

A refactoring that fixes a finding, which the language server plans against the whole workspace when it is asked for: the code action of the refactoring, offered for the range of the diagnostic.

RelatedFinding

A place an AnalyzerFinding is about, besides its own range.

RenameFix

A rename that fixes a finding: the name in the range of the diagnostic, to a name the client's user chooses, or to one of the names the analyzer suggests.

SettingFix

An item added to the list of a setting, which fixes a finding: the name the finding is about, added to the names the analyzer allows (Diagnostics.MeaningfulNames.AllowedNames). The client keeps the list (rdcore/settings/listValue); the platform offers the fix only to a client that expects to be asked to.

SyntaxEdits

The edits of a fix (EditFix), placed by the positions of the syntax tree an analyzer is given: what to write where, without the text around it.

Structs

RDCoreDiagnosticCode

The code a diagnostic is reported under: a prefix of three letters that says who issues it, and a number of five digits, as in XYZ00042 (RD-VBAL §1.1.4).

Interfaces

IModuleAnalyzer

Looks at a module and says what is worth saying about it (RD-VBAL §2.6.4).

Enums

AnalysisPhase

How much of what the platform can find out about a module an analysis waits for.

ProjectChangeKind

What a change of the project (ProjectChange) changes.