Paul Berry
bcd7c3a3e4
In a follow-up CL, I will change the code generator for diagnostic messages so that all code-generated instances of `DiagnosticCode` have `name` and `uniqueName` fields in all lower case letters. This will help pave the way toward resolving conflicts between the diagnostic code naming conventions between the analyzer and CFE. To prepare for this change, the following pieces of code need to first be modified to be case insensitive: - The `_ignoreNullSafetyWarnings` check in `RemoveDeadCodeSoundFlowAnalysisTest`. - The `_diagnosticCodes` fields in `_CannotIgnoreOptionValidator` and `_ErrorFilterOptionValidator`. - The `computeErrorData` methods in `ConstantsDataComputer` and `_InheritanceDataComputer`. - The `_writeDiagnostic` methods in `DriverEventsPrinter` and `ResolvedUnitResultPrinter`. - The `_validateMessages` and `_validateSnippet` methods in `DocumentationValidator`. - The `run` method in `TextualOutline`. In most cases, the code was changed to be case insensitive by having it call `.toLowerCase()` or `.toUpperCase()` on the diagnostic code name before operating on it. In one case I was able to re-use the `AnalyzerCode.lowerSnakeCaseName` getter. Change-Id: I6a6a6964f3cc4c71f2e82478855d64d5ef91d26b Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/465804 Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Commit-Queue: Paul Berry <paulberry@google.com>
analysis_server
A long-running process that provides analysis results to other tools.
The analysis server is designed to provide on-going analysis of one or more code bases as those code bases are changing.
Using the server
The analysis server is not intended to be used stand-alone, and therefore does not have a human-friendly user interface.
Clients (typically tools, such as an editor) are expected to run the analysis
server in a separate process and communicate with it using a JSON protocol. The
original protocol is specified in the file analysis_server/doc/api.html
and Language Server Protocol support is documented in
tool/lsp_spec/README.md.
Features and bugs
Please file feature requests and bugs at the issue tracker.