- 08 Mar, 2017 1 commit
-
-
Alexandre Ardhuin authored
* prefer const constructors * fix double throw
-
- 04 Mar, 2017 1 commit
-
-
Chris Bracken authored
-
- 01 Mar, 2017 1 commit
-
-
Chris Bracken authored
This ensures that both timer/microtask queues are cleared out rather than assuming that all work is completed in a specified amount of time.
-
- 26 Feb, 2017 1 commit
-
-
Adam Barth authored
Fixes #8413
-
- 24 Feb, 2017 1 commit
-
-
Adam Barth authored
It's common to just want a simple colored box. Simple thing should be simple, so this patch adds a convenience argument to Continer for creating a box decoration that is just a color. Fixes #5555
-
- 17 Feb, 2017 2 commits
-
-
Adam Barth authored
Rename all the "2" classes related to scrolling to remove the "2". Now that the old scrolling code is gone, we don't need to use the suffix.
-
Adam Barth authored
All the clients have migrated to Scrollable2.
-
- 09 Feb, 2017 2 commits
-
-
Alexandre Ardhuin authored
-
Ian Hickson authored
Move the back button and drawer opening logic into the app bar. Move the tap-status-bar-to-scroll-to-top logic to using ScrollControllers. Provide a PrimaryScrollController and a `primary` flag on scroll views. Make it possible to track when a route becomes or stops being poppable.
-
- 01 Feb, 2017 1 commit
-
-
Adam Barth authored
This patch removes unnecessary uses of scrollableKey from tests. Scrollable2 will likely use a different mechanism for identifying itself, so we want to focus on the uses of scrollableKey that will need to be addressed in the new implementation.
-
- 24 Jan, 2017 1 commit
-
-
Adam Barth authored
This widget is a replacement for ScrollableViewport that uses the new Scrollable2 machinery. The widget is not based on Slivers but does use the new scroll behavior classes.
-
- 23 Jan, 2017 1 commit
-
-
Ian Hickson authored
...now that we have generic methods, their types need to be specified too.
-
- 22 Jan, 2017 1 commit
-
-
Ian Hickson authored
-
- 09 Dec, 2016 1 commit
-
-
Alexandre Ardhuin authored
-
- 03 Nov, 2016 1 commit
-
-
Ian Hickson authored
People get confused by the tight constraints.
-
- 17 Oct, 2016 1 commit
-
-
Adam Barth authored
Fixes #616
-
- 03 Oct, 2016 1 commit
-
-
Chris Bracken authored
-
- 26 Sep, 2016 1 commit
-
-
Adam Barth authored
The spec forbids persistent bottom sheets from overlapping the app bar. There are also some fancy scroll-linked effects that we're supposed to do with persistent bottom sheets, but those will need to wait for another patch. Fixes #5143
-
- 16 Aug, 2016 1 commit
-
-
Hans Muller authored
-
- 11 Aug, 2016 1 commit
-
-
Jason Simmons authored
Fixes https://github.com/flutter/flutter/issues/5131
-
- 22 Jul, 2016 1 commit
-
-
Adam Barth authored
If the scaffold is new and has a floating action button, we skip the entrance animation for the fab. Fixes #4445
-
- 16 May, 2016 1 commit
-
-
Ian Hickson authored
This makes it possible to substitute 'flutter run' for 'flutter test' and actually watch a test run on a device. For any test that depends on flutter_test: 1. Remove any import of 'package:test/test.dart'. 2. Replace `testWidgets('...', (WidgetTester tester) {` with `testWidgets('...', (WidgetTester tester) async {` 3. Add an "await" in front of calls to any of the following: * tap() * tapAt() * fling() * flingFrom() * scroll() * scrollAt() * pump() * pumpWidget() 4. Replace any calls to `tester.flushMicrotasks()` with calls to `await tester.idle()`. There's a guarding API that you can use, if you have particularly complicated tests, to get better error messages. Search for TestAsyncUtils.
-
- 29 Apr, 2016 1 commit
-
-
Ian Hickson authored
* Refactor widget test framework Instead of: ```dart test("Card Collection smoke test", () { testWidgets((WidgetTester tester) { ``` ...you now say: ```dart testWidgets("Card Collection smoke test", (WidgetTester tester) { ``` Instead of: ```dart expect(tester, hasWidget(find.text('hello'))); ``` ...you now say: ```dart expect(find.text('hello'), findsOneWidget); ``` Instead of the previous API (exists, widgets, widget, stateOf, elementOf, etc), you now have the following comprehensive API. All these are functions that take a Finder, except the all* properties. * `any()` - true if anything matches, c.f. `Iterable.any` * `allWidgets` - all the widgets in the tree * `widget()` - the one and only widget that matches the finder * `firstWidget()` - the first widget that matches the finder * `allElements` - all the elements in the tree * `element()` - the one and only element that matches the finder * `firstElement()` - the first element that matches the finder * `allStates` - all the `State`s in the tree * `state()` - the one and only state that matches the finder * `firstState()` - the first state that matches the finder * `allRenderObjects` - all the render objects in the tree * `renderObject()` - the one and only render object that matches the finder * `firstRenderObject()` - the first render object that matches the finder There's also `layers' which returns the list of current layers. `tap`, `fling`, getCenter, getSize, etc, take Finders, like the APIs above, and expect there to only be one matching widget. The finders are: * `find.text(String text)` * `find.widgetWithText(Type widgetType, String text)` * `find.byKey(Key key)` * `find.byType(Type type)` * `find.byElementType(Type type)` * `find.byConfig(Widget config)` * `find.byWidgetPredicate(WidgetPredicate predicate)` * `find.byElementPredicate(ElementPredicate predicate)` The matchers (for `expect`) are: * `findsNothing` * `findsWidgets` * `findsOneWidget` * `findsNWidgets(n)` * `isOnStage` * `isOffStage` * `isInCard` * `isNotInCard` Benchmarks now use benchmarkWidgets instead of testWidgets. Also, for those of you using mockers, `serviceMocker` now automatically handles the binding initialization. This patch also: * changes how tests are run so that we can more easily swap the logic out for a "real" mode instead of FakeAsync. * introduces CachingIterable. * changes how flutter_driver interacts with the widget tree to use the aforementioned new API rather than ElementTreeTester, which is gone. * removes ElementTreeTester. * changes the semantics of a test for scrollables because we couldn't convince ourselves that the old semantics made sense; it only worked before because flushing the microtasks after every event was broken. * fixes the flushing of microtasks after every event. * Reindent the tests * Fix review comments
-
- 28 Apr, 2016 1 commit
-
-
Adam Barth authored
This patch addresses late-breaking comments on previous patches.
-
- 27 Apr, 2016 1 commit
-
-
Adam Barth authored
This patch adds an option to Scaffold to disable resizing the body to avoid the window padding. This lets developers create layouts that are stable when the keyboard overlays the app. Fixes #3565
-