Konstantin Shcheglov
1309dffc0a
Move the analyzer-only Diagnostic, DiagnosticMessage, Severity, and locatable diagnostic helper types out of _fe_analyzer_shared and into package:analyzer. I paln to make changes outlined in https://github.com/dart-lang/sdk/issues/63311 and chat discussion. Keeping these classes in the analyzer simplifies the migration and avoids introducing a shared abstraction before there is a concrete need for one. If we decide later need to have a shared abstraction, we can always extract one at that point. With coding agents internal code motion is cheap. Update analyzer, analysis server plugin, analyzer plugin, linter, and scanner call sites to import the moved APIs from analyzer libraries, and refresh API baselines to reflect the new public owner. Change-Id: Ie0ef0f01c6e4be7ebaac25619ac3e3fe991a44d9 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/501000 Reviewed-by: Samuel Rawlins <srawlins@google.com> Reviewed-by: Paul Berry <paulberry@google.com> Commit-Queue: Konstantin Shcheglov <scheglov@google.com>
25 lines
736 B
YAML
25 lines
736 B
YAML
name: _fe_analyzer_shared
|
|
# See the release policy for managing this version number at
|
|
# pkg/analyzer/doc/implementation/releasing.md.
|
|
version: 100.0.0
|
|
description: Logic that is shared between the front_end and analyzer packages.
|
|
repository: https://github.com/dart-lang/sdk/tree/main/pkg/_fe_analyzer_shared
|
|
|
|
environment:
|
|
sdk: ^3.11.0
|
|
|
|
resolution: workspace
|
|
|
|
dependencies:
|
|
meta: ^1.9.0
|
|
|
|
# We use 'any' version constraints here as we get our package versions from
|
|
# the dart-lang/sdk repo's DEPS file. Note that this is a special case; the
|
|
# best practice for packages is to specify their compatible version ranges.
|
|
# See also https://dart.dev/tools/pub/dependencies.
|
|
dev_dependencies:
|
|
checks: any
|
|
collection: any
|
|
test: any
|
|
|