Keerti Parthasarathy
43fb59f4dc
- use package_config.json as marker file for workspace. - workspace can have multiple packages, they can be either PubPackages (marker pubspec.yaml) or BasicWorkspace. - add package info (pubspec) to resolution salt. - removed duplication of finding package_config.json from ContextLocator, as this is now done while creating workspace. - some test/s setup/expectations were changed since we now use package config as marker for workspace instead of pubspec. Change-Id: I091a4a686c6b1d8c14858aefd9843a8d9c8efa25 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/345346 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Commit-Queue: Keerti Parthasarathy <keertip@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.