Nicholas Shahan
2379cdc080
- Add a runtime flag to enable checks on non-nullable APIs that return values from non-static JavaScript interop. - Call a new helper method at the call site when these APIs are detected to perform the null check. - Add test file for the cases we can detect and enforce. NOTE: This does not make non-static JavaScript interop sound. This only adds more checks to enforce soundness with respect to nullability in some cases. There are still holes that will never be closed due to the permissive nature of this form of JavaScript interop. Change-Id: I2f88d1543a683fdc84d764e2b0eaafeb0ca73107 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/358581 Reviewed-by: Samuel Rawlins <srawlins@google.com> Reviewed-by: Mayank Patke <fishythefish@google.com> Commit-Queue: Nicholas Shahan <nshahan@google.com> Reviewed-by: Srujan Gaddam <srujzs@google.com> Reviewed-by: Sigmund Cherem <sigmund@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