- 07 Jan, 2021 18 commits
-
-
Justin McCandless authored
This reverts commit 4901744e, which was a minor breaking change that I missed. Will try to open the PR again following the breaking change process.
-
Jenn Magder authored
-
engine-flutter-autoroll authored
-
xster authored
-
engine-flutter-autoroll authored
43ee609f0 [camera_platform_interface] Add platform interface methods for locking capture orientation. (flutter/plugins#3389) (#73469)
-
Justin McCandless authored
-
Nathan Walker authored
-
David LJ authored
-
Kate Lovett authored
-
Jonah Williams authored
-
Zachary Anderson authored
This reverts commit 655cd1e2.
-
engine-flutter-autoroll authored
-
engine-flutter-autoroll authored
-
engine-flutter-autoroll authored
-
engine-flutter-autoroll authored
dac4b6f3c [camera_platform_interface] Add platform interface methods for setting auto focus. (flutter/plugins#3369) (#73436)
-
Ian Hickson authored
-
Ian Hickson authored
-
Ian Hickson authored
* Minor doc, style, and perf updates to Navigator/Routes These are minor fixes I ended up making while working on a larger project that never went anywhere. - Used a ColoredBox instead of a DecoratedBox for ModalBarrier (probably a trivial memory/perf win). - A bunch of Navigator documentation fixes around when things rebuild. - Mark routes dirty when the Navigator has a dependency change. I cannot find a way to test this because as far as I can tell it makes no actual difference to when things rebuild because whenever the Navigator rebuilds the Overlay rebuilds and whenever that happens every OverlayEntry rebuilds, but in theory that's not guaranteed so this is sort of a correctness fix. It may even be a perf loss. We do something similar in didUpdateWidget already. I could be convinced to maybe remove these... - Make ModalRoute.filter public like everything else. - Made ModalRoute update its barrier when it gets an update, in case e.g. the modal barrier depends on inherited widgets via the navigator context. Again, not sure of any way to detect this, it might actually be moot, but it seems to be the technically correct solution? - Minor style fixes. All in all I couldn't figure out a way to test any of this (I wrote multiple large tests but it turns out they all already pass on master and are effectively redundant with existing tests). * Remove extraneous blank line
-
- 06 Jan, 2021 22 commits
-
-
Jonah Williams authored
-
Ian Hickson authored
-
Sam Rawlins authored
-
Jenn Magder authored
This reverts commit 28db5a0f.
-
Jenn Magder authored
-
Jenn Magder authored
-
Jenn Magder authored
-
Jenn Magder authored
-
chunhtai authored
-
Ferhat authored
-
chunhtai authored
-
Chinmoy authored
-
Justin McCandless authored
Allows passing in a TextEditingController and FocusNode to RawAutocomplete, which enables split UIs where the TextField is in another part of the tree from the results.
-
engine-flutter-autoroll authored
-
YeungKC authored
-
engine-flutter-autoroll authored
-
Jonah Williams authored
-
Jonah Williams authored
-
Jonah Williams authored
-
engine-flutter-autoroll authored
-
Shi-Hao Hong authored
* Remove all usage of no_null_safety in API docs workflows
-
Shi-Hao Hong authored
-