Revert "Tweak `expect.dart` library." This reverts commit ff5f391c0a0247f449a959797ecf6e10ba950da2. Reason for revert: The expect library is used by Flutter engine, and some of its tests use assertStatementsEnabled. There should be a migration path that doesn't require an atomic change, like adding the replacement api before removing the old one. Original change's description: > Tweak `expect.dart` library. > > Make API more consistent for a few methods. > Reduce the number of language features used in tests: > * Never iterating an iterable, always converting it > using `.toList()` first and iterating using indices > (fx `setEquals`). > Also require a `List` in places where an `Iterable` > wasn't necessary. > * Avoid doing complicated computations that are also > used for the error message. Do simple check first, > then recompute to get better error messages > (fx `allDistinct`). > > Renamed some rarely used members for consistency > (`stringContainsInOrder`->`containsInOrder`, > where other string-contains functions just start > with `contains`, and `containsOneOf` -> `containsAny` > to match `Iterable.any` phrasing, and also it accepts > if containing at least one, not precisely one.) > > Removed a function that wasn't used anywhere. > > Moved `assertStatementsEnabled` to `variations.dart` as `asserts`. > Removed `typeAssertionsEnabled` and `checkedModeEnabled`. The former used in one place, where it was replaced with `checkedImplicitDowncasts` from `variations.dart`, the latter wasn't used anywhere. > > Deprecates `package:expect/minitest.dart`. It was never intended > to be used for new tests, only as a help to convert existing tests > written against `package:unit_test`. > All existing imports marked as `// ignore: deprecated_member_use`. > > Change-Id: I07e21d4c0f3ccf11b82ee34af2668fdbb22264d2 > Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/352360 > Reviewed-by: Slava Egorov <vegorov@google.com> > Reviewed-by: Ömer Ağacan <omersa@google.com> > Reviewed-by: Nate Bosch <nbosch@google.com> > Reviewed-by: Stephen Adams <sra@google.com> > Commit-Queue: Lasse Nielsen <lrn@google.com> Change-Id: I360b4347470a0bb2b63c3108e2b83ee2a771bf3f No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/362020 Reviewed-by: Nate Bosch <nbosch@google.com> Reviewed-by: Ömer Ağacan <omersa@google.com> Reviewed-by: Stephen Adams <sra@google.com> Reviewed-by: Leaf Petersen <leafp@google.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: William Hesse <whesse@google.com> https://dart.googlesource.com/sdk/+/cd2c566bcf2263e93bef877443a784f3afe35549
Monorepo is:
With depot_tools installed and on your path, create a directory for your monorepo checkout and run these commands to create a gclient solution in that directory:
mkdir monorepo cd monorepo gclient config --unmanaged https://dart.googlesource.com/monorepo gclient sync -D
This gives you a checkout in the monorepo directory that contains:
monorepo/ DEPS - the DEPS used for this gclient checkout commits.json - the pinned commits for Dart, flutter/engine, and flutter/flutter tools/ - scripts used to create monorepo DEPS engine/src/ - the flutter/buildroot repo flutter/ - the flutter/engine repo out/ - the build directory, where Flutter engine builds are created third_party/ - Flutter dependencies checked out by DEPS dart/ - the Dart SDK checkout. third_party - Dart dependencies, also used by Flutter flutter/ - the flutter/flutter repo
Flutter's instructions for building the engine are at Compiling the engine
They can be followed closely, with a few changes:
goma_ctl ensure_start is sufficient.Example build commands that work on linux:
MONOREPO_PATH=$PWD if [[ ! $PATH =~ (^|:)$MONOREPO_PATH/flutter/bin(:|$) ]]; then PATH=$MONOREPO_PATH/flutter/bin:$PATH fi export GOMA_DIR=$(dirname $(command -v gclient))/.cipd_bin goma_ctl ensure_start pushd engine/src flutter/tools/gn --goma --no-prebuilt-dart-sdk --unoptimized --full-dart-sdk autoninja -C out/host_debug_unopt popd
The Flutter commands used to build and run apps will use the locally built Flutter engine and Dart SDK, instead of the one downloaded by the Flutter tool, if the --local-engine option is provided.
For example, to build and run the Flutter spinning square sample on the web platform,
MONOREPO_PATH=$PWD cd flutter/examples/layers flutter --local-engine=host_debug_unopt \ -d chrome run widgets/spinning_square.dart cd $MONOREPO_PATH
To build for desktop, specify the desktop platform device in flutter run as -d macos or -d linux or -d windows. You may also need to run the command
flutter create --platforms=windows,macos,linux
on existing apps, such as sample apps. New apps created with flutter create already include these support files. Details of desktop support are at Desktop Support for Flutter
Tests in the Flutter source tree can be run with the flutter test command, run in the directory of a package containing tests. For example:
MONOREPO_PATH=$PWD cd flutter/packages/flutter flutter test --local-engine=host_debug_unopt cd $MONOREPO_PATH
Please file an issue or email the dart-engprod team with any problems with or questions about using monorepo.
We will update this documentation to address them.
flutter commands may download the engine and Dart SDK files for the configured channel, even though they will be using the local engine and its SDK.gclient sync needs to be run in an administrator session, because some installed dependencies create symlinks.