Sam Rawlins
0ffd2849e4
* OptionsValidator was defined in the `src/plugin/` directory (the only file in there), which I found confusing. Moved it to `src/analysis_options/`. * OptionsFileValidator, and a few related classes, were defined in the `src/task/` (the last file in there!), so I moved it to the same place. There is more to tidy in here, but this is a simple file-move. Change-Id: I8f4c5cc0ae4e76eb6c17249457c50ab69c82590d Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/443147 Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Commit-Queue: Samuel Rawlins <srawlins@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.