Files
sdk/pkg/linter/pubspec.yaml
T
Paul Berry a25eb56b70 Allow linter unit tests to be run from any directory.
I frequently run unit tests from the root directory of the SDK
package. Previous to this CL, that didn't work for the `linter`
package, because the test `validate_sdk_version_map.dart` contained a
hard-coded path that only worked if the test was invoked from the
`pkg/linter` subdirectory.

With this change, the test uses the `packageRoot` getter from the
`analyzer_utilities` package, which locates the SDK's `pkg` directory
using heuristics that work from a variety of different starting
directories, including the root of the SDK repo, anywhere within
`pkg/linter`, and in a Google3 bazel test.

Change-Id: I525ad21cb5228e670dadc98c05de18bddf3912e1
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/339660
Reviewed-by: Phil Quitslund <pquitslund@google.com>
Commit-Queue: Paul Berry <paulberry@google.com>
2023-12-04 22:39:37 +00:00

32 lines
697 B
YAML

name: linter
# This package is not intended for consumption on pub.dev. DO NOT publish.
publish_to: none
description: >-
The implementation of the lint rules supported by the analyzer framework.
This package is not intended to be used directly.
environment:
sdk: ^3.2.0-edge
# Use 'any' constraints here; we get our versions from the DEPS file.
dependencies:
analyzer: any
collection: any
meta: any
path: any
pub_semver: any
source_span: any
yaml: any
# Use 'any' constraints here; we get our versions from the DEPS file.
dev_dependencies:
analyzer_utilities: any
args: any
cli_util: any
glob: any
http: any
lints: any
test: any
test_reflective_loader: any