Sam Rawlins
155a64c1b7
This bumps the Registry class to be able to take "rules that are enabled by default" and "rules that need to be explicitly enabled", "lint rules" and "warning rules". Next is to improve the classes. Add parsing for the top-level `plugins` section, and `PluginConfiguration` class to hold this data, and `get pluginConfigurations` on AnalysisOptions. Rename `parseLintRuleConfigs` to `parseLinterSection` to align better with the other functions in engine.dart. Rename `_ruleConfigs` function to `parseRulesSection`. Change-Id: Ib93b7548bfb13cc94381971a5a2780a5dc81e9f1 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/392040 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: Phil Quitslund <pquitslund@google.com> Commit-Queue: Samuel Rawlins <srawlins@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.