6399be62d2
## Description Removes the `flutter_test` dependency on `quiver`, instead using the more targeted `clock` and `fake_async` packages. ## Related Issues https://github.com/flutter/flutter/issues/53908 ## Tests No changes to tests ## Checklist Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (`[x]`). This will ensure a smooth and quick review process. - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I signed the [CLA]. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] All existing and new tests are passing. - [x] The analyzer (`flutter analyze --flutter-repo`) does not report any problems on my PR. - [x] I am willing to follow-up on review comments in a timely manner. ## Breaking Change Did any tests fail when you ran them? Please read [Handling breaking changes]. - [ ] No, no existing tests failed, so this is *not* a breaking change. - [x] Yes, this is a breaking change. *If not, delete the remainder of this section.* - [x] I wrote a design doc: https://docs.google.com/document/d/1EkkLbECNBwHgddBQAZqEy7iQLTIxR1rgChKzxcLwhio/edit - [x] I got input from the developer relations team, specifically from: @RedBrogdon - [x] I wrote a migration guide: https://github.com/flutter/website/pull/3932 <!-- Links --> [issue database]: https://github.com/flutter/flutter/issues [Contributor Guide]: https://github.com/flutter/flutter/wiki/Tree-hygiene#overview [Test Coverage]: https://github.com/flutter/flutter/wiki/Test-coverage-for-package%3Aflutter [Flutter Style Guide]: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo [Features we expect every widget to implement]: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [Tree Hygiene]: https://github.com/flutter/flutter/wiki/Tree-hygiene [Handling breaking changes]: https://github.com/flutter/flutter/wiki/Tree-hygiene#handling-breaking-changes
Samples Catalog
A collection of sample apps that demonstrate how Flutter can be used.
Each sample app is contained in a single .dart file located in the lib
directory. To run each sample app, specify the corresponding file on the
flutter run command line, for example:
flutter run lib/animated_list.dart
flutter run lib/app_bar_bottom.dart
flutter run lib/basic_app_bar.dart
...
The apps are intended to be short and easily understood. Classes that represent the sample's focus are at the top of the file; data and support classes follow.
Each sample app contains a comment (usually at the end) which provides some standard documentation that also appears in the web view of the catalog. See the "Generating..." section below.
Generating the web view of the catalog
Markdown and a screenshot of each app are produced by bin/sample_page.dart
and saved in the .generated directory. The markdown file contains
the text taken from the Sample Catalog comment found in the app's source
file, followed by the source code itself.
This sample_page.dart command line app must be run from the examples/catalog
directory. It relies on templates also found in the bin directory, and it
generates and executes test_driver apps to collect the screenshots:
cd examples/catalog
dart bin/sample_page.dart