Brian Wilkerson
0d9c03b6a3
At this point I'm mostly interested in getting your feedback on the general approach of making the fix processor be table driven. If you agree that it's a good direction, then I would actually propose adding a static method to each of the producer classes that looks something like static AddRequiredKeyword generator() => AddRequiredKeyword(); and updating the map to contain references to those static methods (rather than local closures), such as: CompileTimeErrorCode.MISSING_DEFAULT_VALUE_FOR_PARAMETER: const [ AddRequiredKeyword.generator, ], Doing so would make the code in FixProcessor slightly cleaner, and would allow the tables to be constants. Change-Id: Ifdd8a4d82c6ab83aea0929dc9c8a4dcbce271e6f Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/146064 Commit-Queue: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: Konstantin Shcheglov <scheglov@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 (less complete) 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.