- 27 Nov, 2019 1 commit
-
-
Ian Hickson authored
* Update project.pbxproj files to say Flutter rather than Chromium Also, the templates now have an empty organization so that we don't cause people to give their apps a Flutter copyright. * Update the copyright notice checker to require a standard notice on all files * Update copyrights on Dart files. (This was a mechanical commit.) * Fix weird license headers on Dart files that deviate from our conventions; relicense Shrine. Some were already marked "The Flutter Authors", not clear why. Their dates have been normalized. Some were missing the blank line after the license. Some were randomly different in trivial ways for no apparent reason (e.g. missing the trailing period). * Clean up the copyrights in non-Dart files. (Manual edits.) Also, make sure templates don't have copyrights. * Fix some more ORGANIZATIONNAMEs
-
- 22 Nov, 2019 1 commit
-
-
Greg Spencer authored
No code changes, just comments: I spell-checked all the comments in the repo.
-
- 19 Nov, 2019 1 commit
-
-
Alexandre Ardhuin authored
* implicit-casts:false on flutter_tools/lib * address review comments * use castStringKeyedMap * introduce {bool,string,strings}Arg * fix ci
-
- 23 Oct, 2019 1 commit
-
-
Jonah Williams authored
-
- 22 Oct, 2019 2 commits
-
-
Jonah Williams authored
This reverts commit 3597bae6.
-
Ian Hickson authored
-
- 11 Oct, 2019 1 commit
-
-
Ian Hickson authored
-
- 08 Oct, 2019 1 commit
-
-
Jonah Williams authored
-
- 03 Oct, 2019 1 commit
-
-
Zachary Anderson authored
-
- 24 Sep, 2019 1 commit
-
-
Alexandre Ardhuin authored
-
- 13 Sep, 2019 1 commit
-
-
Zachary Anderson authored
-
- 12 Sep, 2019 1 commit
-
-
Zachary Anderson authored
-
- 24 Jul, 2019 1 commit
-
-
Ian Hickson authored
-
- 19 Jul, 2019 1 commit
-
-
Todd Volkert authored
When we were running `pub` within `flutter pub`, we were unconditionally including the `--verbosity=warning` argument. Then we were conditionally including `--verbose` if we were running in verbose mode. However, the former argument supersedes the latter, and we were never able to run `pub` in verbose mode.
-
- 02 Jul, 2019 1 commit
-
-
Alexandre Ardhuin authored
* more ui-as-code * address review comments
-
- 27 Jun, 2019 1 commit
-
-
Alexandre Ardhuin authored
-
- 23 May, 2019 1 commit
-
-
Devon Carew authored
-
- 21 May, 2019 1 commit
-
-
Michael Thomsen authored
-
- 09 Apr, 2019 1 commit
-
-
Michael Thomsen authored
-
- 27 Mar, 2019 1 commit
-
-
Jonah Williams authored
-
- 22 Mar, 2019 1 commit
-
-
Alexandre Ardhuin authored
-
- 20 Mar, 2019 1 commit
-
-
Jonah Williams authored
-
- 15 Mar, 2019 1 commit
-
-
Jonah Williams authored
-
- 11 Mar, 2019 1 commit
-
-
Paul Berry authored
Substantially reduces the danger that a bug in the analysis server might prevent errors from being detected by `flutter analyze`.
-
- 07 Mar, 2019 1 commit
-
-
Jonah Williams authored
-
- 01 Mar, 2019 1 commit
-
-
Alexandre Ardhuin authored
* add trailing commas on list/map/parameters * add trailing commas on Invocation with nb of arg>1 * add commas for widget containing widgets * add trailing commas if instantiation contains trailing comma * revert bad change
-
- 21 Feb, 2019 1 commit
-
-
Alexandre Ardhuin authored
-
- 13 Feb, 2019 1 commit
-
-
Dan Field authored
-
- 05 Feb, 2019 1 commit
-
-
xster authored
-
- 29 Jan, 2019 1 commit
-
-
Alexandre Ardhuin authored
-
- 26 Jan, 2019 1 commit
-
-
Jonah Williams authored
-
- 19 Jan, 2019 1 commit
-
-
Ian Hickson authored
These are essentially self-inflicted race conditions. Instead of timeouts we're going to try a more verbose logging mechanism that points out when things are taking a long time.
-
- 21 Dec, 2018 2 commits
-
-
Ian Hickson authored
This reverts commit 76f70810.
-
Ian Hickson authored
* Remove many timeouts. These are essentially self-inflicted race conditions. Instead of timeouts we're going to try a more verbose logging mechanism that points out when things are taking a long time. * Get the attach tests to pass. * Apply review comments from Todd * More review comment fixes * Put back the extended timeouts here now that I know why we have them...
-
- 17 Oct, 2018 1 commit
-
- 11 Oct, 2018 1 commit
-
-
Greg Spencer authored
This attempts to re-land #22656. There are two changes from the original: I turned off wrapping completely when not sending output to a terminal. Previously I had defaulted to wrapping at and arbitrary 100 chars in that case, just to keep long messages from being too long, but that turns out the be a bad idea because there are tests that are relying on the specific form of the output. It's also pretty arbitrary, and mostly people sending output to a non-terminal will want unwrapped text. I found a better way to terminate ANSI color/bold sequences, so that they can be embedded within each other without needed quite as complex a dance with removing redundant sequences. As part of these changes, I removed the Logger.supportsColor setter so that the one source of truth for color support is in AnsiTerminal.supportsColor. * Turn on line wrapping again in usage and status messages, adds ANSI color to doctor and analysis messages. (#22656) This turns on text wrapping for usage messages and status messages. When on a terminal, wraps to the width of the terminal. When writing to a non-terminal, wrap lines at a default column width (currently defined to be 100 chars). If --no-wrap is specified, then no wrapping occurs. If --wrap-column is specified, wraps to that column (if --wrap is on). Adds ANSI color to the doctor and analysis output on terminals. This is in this PR with the wrapping, since wrapping needs to know how to count visible characters in the presence of ANSI sequences. (This is just one more step towards re-implementing all of Curses for Flutter. :-)) Will not print ANSI sequences when sent to a non-terminal, or of --no-color is specified. Fixes ANSI color and bold sequences so that they can be combined (bold, colored text), and a small bug in indentation calculation for wrapping. Since wrapping is now turned on, also removed many redundant '\n's in the code.
-
- 06 Oct, 2018 2 commits
-
-
Greg Spencer authored
Revert "Turn on line wrapping in usage and status messages, adds ANSI color to doctor and analysis messages. (#22656)" (#22759) This reverts commit e4386321 because it breaks 160 benchmarks, and several devicelab tests, due to changing the format of the output.
-
Greg Spencer authored
Turn on line wrapping in usage and status messages, adds ANSI color to doctor and analysis messages. (#22656) This turns on text wrapping for usage messages and status messages. When on a terminal, wraps to the width of the terminal. When writing to a non-terminal, wrap lines at a default column width (currently defined to be 100 chars). If --no-wrap is specified, then no wrapping occurs. If --wrap-column is specified, wraps to that column (if --wrap is on). Adds ANSI color to the doctor and analysis output on terminals. This is in this PR with the wrapping, since wrapping needs to know how to count visible characters in the presence of ANSI sequences. (This is just one more step towards re-implementing all of Curses for Flutter. :-)) Will not print ANSI sequences when sent to a non-terminal, or of --no-color is specified. Fixes ANSI color and bold sequences so that they can be combined (bold, colored text), and a small bug in indentation calculation for wrapping. Since wrapping is now turned on, also removed many redundant '\n's in the code.
-
- 05 Oct, 2018 2 commits
-
-
Yegor authored
* first pass * revert WidgetsBindingObserver * disable prefer_mixin * docs and more mixins * newer engine; binding fixes * upgrade dependencies * fix test binding * remove whitespace * remove the obsolete `enableSuperMixins: true` * upgrade dartdoc to 0.22.0 * temporarily use git version of dartdoc * fix pub global activate syntax * use dartdoc 0.23.0