Files

T

Konstantin Shcheglov 8bbe6fbdfe Elements. Report analyzer_use_new_elements without any txt file, add file ignores.

Change-Id: I13125f93a6633563ed6853a622bd9fec045bfc0c
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/403923
Commit-Queue: Konstantin Shcheglov <scheglov@google.com>
Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>

2025-01-10 15:20:59 -08:00

lib

[CQ] add feature isEnabled utility

2025-01-07 13:18:28 -08:00

test

CQ. Remove unnecessary 'async' where no 'await'.

2025-01-06 15:16:40 -08:00

analysis_options.yaml

Track migration in 5 more packages

2024-10-18 17:03:29 +00:00

CONTRIBUTING.md

linter: add contributing docs about closing issues

2024-04-23 20:43:10 +00:00

LICENSE

…

OWNERS

…

pubspec.yaml

analyzer packages: Add dependency overrides and comments

2024-12-03 17:44:28 +00:00

README.md

…

README.md

analysis_server_plugin package

This package is being developed for the second incarnation of Dart Analyzer plugins. It is in an intermediate state, and a few things must be kept in mind during this phase of development:

This package is not to be published on pub yet. We will flesh out a stable API befoure the first publish.
In order to support the above point, no pub-publishable code can depend on this package. At no point can we introduce a dependency from a package like analyzer or analyzer_plugin to this package. If we did so, then at the next time we published that package to pub, we would need to publish this package to pub. No. In short, I think what this means is that only the analysis_server package can depend on this package.

Migration of code between packages

As part of the design of the new Dart Analyzer plugins, much code will shift around, in a few directions.

analysis_server package to analysis_server_plugin package: The API of the new Dart Analyzer plugins focuses around two primary concepts: lint rules and quick fixes. Quick assists may be chosen as a third important concept. Lint rule code has typically lived in the analyzer package, and does not need to move. (It's presence in the analyzer package could be deprecated in favor of this package, but it is not important for the implementation.)

Quick fixes, however, have only existed in concept, and interface, and API, in the analysis_server package. That code needs to move to this package in order to be used in a Dart Analyzer plugin.

A move from the analysis_server package to this package is not a breaking change.
analyzer_plugin package to analysis_server_plugin package: Care is being taken to decide where Dart Analyzer plugin code will live and how it will be published. It is not decided yet what the ultimate package API will be. Some code from analyzer_plugin may move to this package.

A move from the analyzer_plugin package is a breaking change. Extreme care must be taken.
analyzer_plugin package to analysis_server package: There will be many components of the analysis server that currently live in analyzer_plugin, because they were necessary for the first version of Dart Analyzer plugins), but are not part of the new Dart Analyzer plugins. These components can be moved safely back into the analysis_server package.

In terms of priority, it is not crucial for such code to be moved out of the analyzer_plugin package. It can live there indefinitely, and the analysis_server package can continue to depend on code from the analyzer_plugin package, as shipped in the SDK.

A move from the analyzer_plugin package is a breaking change. Extreme care must be taken.