Jens Johansen
f908dc692f
Often when rebasing I get conflicts in pkg/_fe_analyzer_shared/lib/src/messages/codes_generated.dart which is a generated file. This should generally be fine, because I can just regenerate it. Except that the code regenerating it uses the very file, so I can't run it. Until now I've had to revert the changes in the file and then run the generate script. This CL adds a "failsafe" version that doesn't use the file, but doesn't directly format it either, then calls the original script which will also format it. Call with something like ``` out/ReleaseX64/dart pkg/front_end/tool/_fasta/generate_messages_failsafe.dart ``` Change-Id: Ic395c7b378b245b41b6fe194affaa6c64ca482db Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/349481 Reviewed-by: Johnni Winther <johnniwinther@google.com> Commit-Queue: Jens Johansen <jensj@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. Its 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