dart-sdk/pkg/analyzer_cli
Konstantin Shcheglov 4eb511da43 Replace more Bazel with Blaze, some simplifications.
Change-Id: I096860e17ce56c2f602718f11706f24989c1f65b
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/255141
Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>
Commit-Queue: Konstantin Shcheglov <scheglov@google.com>
2022-08-15 19:50:46 +00:00
..
bin Remove build mode from analyzer_cli. 2021-03-12 17:05:37 +00:00
lib Remove more unused analyzer_cli options for strong mode, implicit casts, implicit dynamic, and declaration-casts. 2022-08-03 17:16:35 +00:00
test Replace more Bazel with Blaze, some simplifications. 2022-08-15 19:50:46 +00:00
tool [analysis_server] Make CompilationUnit.lineInfo non-nullable 2022-03-03 06:59:00 +00:00
.gitignore Add intellij metadata to the repo. 2017-02-10 12:47:06 -08:00
analysis_options.yaml Enable more lints in analyzer_cli/ 2022-03-07 19:53:53 +00:00
LICENSE Update LICENSE 2021-04-07 10:28:38 +00:00
OWNERS [infra] Add OWNERS to the Dart SDK 2022-02-14 14:06:34 +00:00
pubspec.yaml [pkg] prefer 'any' deps for package dev dependencies 2022-05-27 01:34:59 +00:00
README.md Tweak dartanalyzer readme now that the package is only intended for internal use 2022-07-20 16:03:48 +00:00

SDK development code analysis

dartanalyzer used to be the tool for statically analyzing dart code at the command line. However, this tool has been replaced with dart analyze for this purpose in current SDKs and will no longer be published on pub.

Do not depend on the command line interface or other semantics in this directory as it is now an internal tool for SDK development, used as the dart2analyzer "compiler" for tools/test.py in the SDK. It is configured as part of the test runner, here.

SDK development usage

For SDK development, run analysis from the test tool to validate analysis conclusions on language samples in the testing directory. From the root of the SDK:

tools/test.py --build --use-sdk -c dart2analyzer co19_2 language_2

This will build the Dart VM and compile dartanalyzer into a snapshot, then use that snapshot while analyzing those directories under testing/. Without --use-sdk, test.py will use the source code version of the analyzer instead of the compiled one, which can be useful for debugging.