Srujan Gaddam
3b294fdab2
Closes https://github.com/dart-lang/sdk/issues/54138 Adds a helper to do better type-checks so that users don't accidentally using is checks or have to manually do the right typeof or instanceof checks. In order to do this, there is some refactoring to make ExportCreator a SharedInteropTransformer (as it's shared across all backends) so that we can reuse an existing visitor. In the same class, we remove unnecessary setting of parent pointers. We should clean up the fileOffsets as well, but dart2js verifies that those are set, so we keep them as is for now. Also adds some static errors for edge cases. CoreLibraryReviewExempt: Helper for web-specific library. Change-Id: I34d818ada1349b69afd15d170d3fafa0460f65fa Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/347225 Reviewed-by: Sigmund Cherem <sigmund@google.com> Commit-Queue: Srujan Gaddam <srujzs@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