Daco Harkes
2273611355
This CL organizes the commands in the Dart CLI to categories. It mirrors the categories used in `flutter --help`: `SDK`, `Project`, and `Tools`. The available command section will now look as follows in verbose mode: ``` Available commands: Project build Build a Dart application including native assets. compile Compile Dart to various formats. create Create a new Dart project. pub Work with packages. run Run a Dart program. test Run tests for a project. Source code analyze Analyze Dart code in a directory. doc Generate API documentation for Dart projects. fix Apply automated fixes to Dart source code. format Idiomatically format Dart source code. Tools compilation-server Control resident frontend compilers. development-service Start Dart's development service. devtools Open DevTools (optionally connecting to an existing application). info Show diagnostic information about the installed tooling. language-server Start Dart's analysis server. tooling-daemon Start Dart's tooling daemon. ``` Bug: https://github.com/dart-lang/sdk/issues/60980 Change-Id: Ic9da297fcdd0f8e85d619632ba8ec30fd2c32666 Cq-Include-Trybots: luci.dart.try:pkg-linux-debug-try,pkg-linux-release-arm64-try,pkg-linux-release-try,pkg-mac-release-arm64-try,pkg-mac-release-try,pkg-win-release-arm64-try,pkg-win-release-try Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/436382 Reviewed-by: Michael Thomsen <mit@google.com> Commit-Queue: Daco Harkes <dacoharkes@google.com>
Package validation
The packages in pkg/ are automatically validated on the LUCI CI bots. The
validation is largely done by the tools/package_deps package; it can be tested
locally via:
dart tools/package_deps/bin/package_deps.dart
Packages which are published
There are several packages developed in pkg/ which are published to pub.
Validation of these packages is particularly important because the pub tools are
not used for these packages during development; we get our dependency versions
from the DEPS file. It's very easy for the dependencies specified in a package's
pubspec file to get out of date wrt the packages and versions actually used.
In order to better ensure we're publishing correct packages, we validate some properties of the pubspec files on our CI system. These validations include:
- that the dependencies listed in the pubspec are used in the package
- that all the packages used by the source are listed in the pubspec
- that we don't use relative path deps to pkg/ or third_party/ packages
Packages which are not published
For packages in pkg/ which we do not intend to be published, we put the following comment in the pubspec.yaml file:
# This package is not intended for consumption on pub.dev. DO NOT publish.
publish_to: none
These pubspecs are still validated by the package validation tool. The contents are more informational as the pubspecs for these packages are not consumed by the pub tool or ecosystem.
We validate:
- that the dependencies listed in the pubspec are used in the package
- that all the packages used by the source are listed in the pubspec
- that a reference to a pkg/ package is done via a relative path dependency
Adding new packages
Run gclient sync to re-generate .dart_tool/package_config.json after adding
a new package.
Testing packages
Currently dart test can't be used to run the tests, use test.py as usual.
E.g. the command ./tools/test.py -n...<path> runs all tests with prefix
<path>.