Paul Berry
ca2d428f99
Moving forward, the Dart Model team will own the following packages: - _fe_analyzer_shared - analyzer - analyzer_cli - analyzer_utilities - front_end - frontend_server - kernel - testing In follow-up CLs I will create an OWNERS file for the developer experience team, and then remove the OWNERS files for the old analyzer and CFE teams. Change-Id: Id7cf38ea41a6d3f9ca44f43fae1f310426a31e29 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/409841 Reviewed-by: Kevin Moore <kevmoo@google.com> Commit-Queue: Paul Berry <paulberry@google.com> Reviewed-by: Johnni Winther <johnniwinther@google.com>
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.