languages/dart-sdk
languages/dart-sdk
1
0
Fork 0
mirror of https://github.com/dart-lang/sdk synced 2024-09-16 04:16:51 +00:00
Code Issues Packages Projects Releases Wiki Activity
dart-sdk/pkg/analyzer_cli
History
Konstantin Shcheglov 1b9cc28879 CQ. Make FileSource API, move to lib/source. 
Change-Id: I981d3f0904917ada322ca06448f03ff33ae1f095
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/369360
Commit-Queue: Konstantin Shcheglov <scheglov@google.com>
Reviewed-by: Samuel Rawlins <srawlins@google.com>
2024-06-03 00:36:59 +00:00
..
bin Remove build mode from analyzer_cli. 2021-03-12 17:05:37 +00:00
lib CQ. Make FileSource API, move to lib/source. 2024-06-03 00:36:59 +00:00
test Improve sort_pub_dependencies.dart messages 2024-02-02 18:27:50 +00:00
tool CQ. Stop exporting src/file_system/file_system.dart 2024-05-31 14:55:02 +00:00
.gitignore
analysis_options.yaml [pkg] remove duplicate config from the analysis options files 2023-11-14 00:37: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 Enable language 3.0 for analyzer_cli/. 2023-04-06 19:04:38 +00:00
README.md Remove the legacy "_2" tests. \o/ 2023-11-17 20:17:23 +00:00

README.md

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 language

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.