Paul Berry
643733b42e
(Part of https://github.com/dart-lang/sdk/issues/63288) Updates the `CodeGenerator` mixin so that it outputs `ignore_for_file` comments to ignore the following lints: - unnecessary_type_name_in_constructor - unnecessary_ignore - duplicate_ignore This mixin is used by the code generators that produce the Dart wrappers for the analysis server and analyzer plugin wire protocols. This is a first step towards migrating the packages `analysis_server`, `analysis_server_client`, and `analyzer_plugin` packages to use the new constructor declaration syntax, since it will allow the `unnecessary_type_name_in_constructor` lint to be enabled without breaking generated code. Once all the packages have had their SDK constraints bumped to a language version that supports the new syntax, I'll update the code generator to use the new syntax, and remove the ignores. For more information about the new constructor declaration syntax, see https://github.com/dart-lang/language/blob/main/accepted/future-releases/primary-constructors/feature-specification.md#abbreviations-of-in-body-constructor-declarations. Change-Id: Ied17e3ea772546675aad48efc324f6f16a6a6964 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/505521 Commit-Queue: Paul Berry <paulberry@google.com> Reviewed-by: 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.