Sam Rawlins
ab909226e3
Currently, the `AnalysisContextCollectionImpl` constructor has a callback parameter, `updateAnalysisOptions2`, which has 3 required parameters. The caller can then pass in a closure which accepts those parameters, and updates analysis options. I find this to be a bit of an awkward API, and a little bit complex, so it would be good if we can simplify it. It is all private impl, but it is used in a few codebases, I believe. Dartdoc is one. So, it looked to me like none of the callers _use_ the `ContextRoot` parameter, so it would be good to simplify here, and remove it from the callback signature. This is _not_ the final API I'm looking for. Just an incremental step, and since it is private API, it doesn't need to be in a major release of analyzer. Change-Id: Iad9da9f36e817add0bd8c49975ecd14311588661 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/392204 Commit-Queue: Samuel Rawlins <srawlins@google.com> Reviewed-by: Konstantin Shcheglov <scheglov@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.