- 20 Jun, 2019 1 commit
-
-
Jacob Richman authored
Breaking change to extremely rarely used ParentDataWidget.debugDescribeInvalidAncestorChain api changing the return type of the method from String to DiagnosticsNode.
-
- 16 May, 2019 1 commit
-
-
Greg Spencer authored
This adds a reverseDuration parameter to AnimationController so that the animation has a different duration when going in reverse as it does going forward.
-
- 04 Apr, 2019 1 commit
-
-
Michael Goderbauer authored
-
- 29 Jan, 2019 1 commit
-
-
Alexandre Ardhuin authored
-
- 24 Jan, 2019 2 commits
-
-
Frederik Schweiger authored
-
Dan Field authored
-
- 22 Jan, 2019 1 commit
-
-
jslavitz authored
* Changes Cupertino page transition curves to make paging animations more similar to those of native iOS
-
- 08 Nov, 2018 1 commit
-
-
Greg Spencer authored
This converts existing ## Sample code samples to {@tool sample}...{@end-tool} form. Also: 1. Fixed a minor bug in analyze-sample-code.dart 2. Made the snippet tool only insert descriptions if the description is non-empty. 3. Moved the Card diagram to before the code sample.
-
- 05 Nov, 2018 1 commit
-
-
Greg Spencer authored
This rewrites the sample code analysis script to be a little less of a hack (but still not pretty), and to handle snippets as well. It also changes the semantics of how sample code is handled: the namespace for the sample code is now limited to the file that it appears in, so some additional "Examples can assume:" blocks were added. The upside of this is that there will be far fewer name collisions. I fixed the output too: no longer will you get 4000 lines of numbered output with the error at the top and have to grep for the actual problem. It gives the filename and line number of the original location of the code (in the comment in the tree), and prints out the source code on the line that caused the problem along with the error. For snippets, it prints out the location of the start of the snippet and the source code line that causes the problem. It can't print out the original line, because snippets get formatted when they are written, so the line might not be in the same place.
-
- 17 Oct, 2018 1 commit
-
-
Alexandre Ardhuin authored
* enable lint prefer_void_to_null * replace last Null by void
-
- 16 Oct, 2018 1 commit
-
-
Alexandre Ardhuin authored
* Future<void> main * Future<void>.delayed * prefer_void_to_Null * address review comments
-
- 23 Sep, 2018 1 commit
-
-
Ian Hickson authored
-
- 12 Sep, 2018 1 commit
-
-
Alexandre Ardhuin authored
* enable lint unnecessary_new * fix tests * fix tests * fix tests
-
- 07 Sep, 2018 1 commit
-
-
Jonah Williams authored
-
- 29 Aug, 2018 1 commit
-
-
- 23 Aug, 2018 1 commit
-
-
Jonah Williams authored
-
- 02 Aug, 2018 1 commit
-
-
Alexandre Ardhuin authored
-
- 27 Jul, 2018 1 commit
-
-
Todd Volkert authored
It was causing problems rolling Flutter into Fuchsia
-
- 23 Jul, 2018 1 commit
-
-
Alexandre Ardhuin authored
* re-enable lint unnecessary_const * remove trailling whitespaces * remove unnecessary const (after merge)
-
- 16 Jul, 2018 2 commits
-
-
Ian Hickson authored
This reverts commit cc1cf13e.
-
Alexandre Ardhuin authored
-
- 05 Jun, 2018 1 commit
-
-
Alexandre Ardhuin authored
-
- 12 Mar, 2018 1 commit
-
-
Jason Simmons authored
-
- 02 Feb, 2018 1 commit
-
-
Alexandre Ardhuin authored
-
- 09 Jan, 2018 1 commit
-
-
Ian Hickson authored
-
- 22 Nov, 2017 1 commit
-
-
Kyle Bradshaw authored
* AnimationController reset() method Just a simple convenience method to fix #13039 * Added `reset()` test * More test expectations Per feedback. * Removed test print * Improved documentation of reset() * Add controller.reverse to test
-
- 17 Nov, 2017 1 commit
-
-
Greg Spencer authored
I got tired of drive-by spelling fixes, so I figured I'd just take care of them all at once. This only corrects errors in the dartdocs, not regular comments, and I skipped any sample code in the dartdocs. It doesn't touch any identifiers in the dartdocs either. No code changes, just comments.
-
- 21 Sep, 2017 1 commit
-
-
Alexandre Ardhuin authored
-
- 23 Aug, 2017 1 commit
-
-
Brenton Simpson authored
`stiffness` is the name of a spring's `k` input on [iOS](https://developer.apple.com/documentation/quartzcore/caspringanimation), [Android](https://developer.android.com/topic/libraries/support-library/preview/spring-animation.html), and the [Web](https://github.com/skevy/wobble/blob/bbc0f831e234f2d24fb905f2ec278c134d69ed68/src/index.js#L11-L22). To ensure the API is familiar to and easily understood by developers coming from other platforms, Flutter should follow this convention as well. This is a minimally-breaking change. Across [all of GitHub](https://github.com/search?l=Dart&q=springConstant&type=Code&utf8=%E2%9C%93), there are only 2 uses of the `springConstant` API (in Mondrian). Those can be easily changed to use this name. Closes #11684
-
- 18 Aug, 2017 1 commit
-
-
Jacob Richman authored
when describing non-nullable method arguments.
-
- 04 Aug, 2017 3 commits
-
-
Michael Goderbauer authored
* Adding tests for animationStatus * remove comments * animateTo is allways forward * clearify docs * review comments
-
Michael Goderbauer authored
-
Michael Goderbauer authored
* Do not schedule animation if already at the target value * Partially fixes https://github.com/flutter/flutter/issues/11495. * Also includes a fix for Cupertino button to always run the tap animation even if the finger is immediately lifted from the screen (uncovered by a test failure). * refactorings * more tests * test clearifications * remove Listener * fix lints * fix async issue
-
- 12 Jun, 2017 1 commit
-
-
Ian Hickson authored
-
- 05 Jun, 2017 1 commit
-
-
Alexandre Ardhuin authored
-
- 05 May, 2017 1 commit
-
-
Ian Hickson authored
-
- 03 May, 2017 1 commit
-
-
Ian Hickson authored
-
- 15 Apr, 2017 1 commit
-
-
Ian Hickson authored
With this patch, you can do: ```dart Future<Null> foo() async { try { await controller.forward().orCancel; await controller.reverse().orCancel; await controller.forward().orCancel; } on TickerCanceled { // did not complete } } ``` ...in a State's async method, and so long as you dispose of the controller properly in your dispose, you'll have a nice way of doing animations in sequence without leaking the controller. try/finally works as well, if you need to allocate resources and discard them when canceled. Simultaneously, you can do: ```dart Future<Null> foo() async { await controller.forward().orCancel; await controller.reverse().orCancel; await controller.forward().orCancel; } ``` ...and have the same effect, where the method will just silently hang (and get GC'ed) if the widget is disposed, without leaking anything, if you don't need to catch the controller being killed. And all this, without spurious errors for uncaught exceptions on controllers.
-
- 16 Mar, 2017 1 commit
-
-
Hans Muller authored
-
- 04 Mar, 2017 1 commit
-
-
Chris Bracken authored
Covers lib/ in package:flutter.
-