- 05 Nov, 2019 1 commit
-
-
Zachary Anderson authored
-
- 18 Oct, 2019 3 commits
-
-
Ian Hickson authored
See #41880 for history.
-
Jonah Williams authored
This reverts commit 1781d5c9.
-
Ian Hickson authored
-
- 14 Oct, 2019 1 commit
-
-
Jenn Magder authored
-
- 11 Oct, 2019 1 commit
-
-
Ian Hickson authored
...because otherwise, processes that think they're manipulating your filesystem will be doing crazy things the test is ignoring, leading to (at best) failures and (at worst) flakes or disk corruption.
-
- 08 Oct, 2019 1 commit
-
-
Jonah Williams authored
-
- 07 Oct, 2019 1 commit
-
-
Zachary Anderson authored
-
- 06 Oct, 2019 1 commit
-
-
Ian Hickson authored
* Minor clean-up in terminal.dart * Don't wrap text in tests (otherwise we'll be sensitive to the terminal width).
-
- 03 Oct, 2019 1 commit
-
-
Zachary Anderson authored
-
- 30 Sep, 2019 1 commit
-
-
Zachary Anderson authored
* [flutter_tool] Report to analytics when the tool is killed by a signal * Fix analyzer lint
-
- 16 Sep, 2019 1 commit
-
-
Zachary Anderson authored
-
- 13 Sep, 2019 1 commit
-
-
Zachary Anderson authored
-
- 05 Sep, 2019 1 commit
-
-
stuartmorgan authored
Avoids unnecessarily breaking projects that have another .xcodeproj in their macos/ directory, which worked until the addition of the getInfo call.
-
- 28 Aug, 2019 1 commit
-
-
Zachary Anderson authored
-
- 22 Aug, 2019 1 commit
-
-
Jenn Magder authored
-
- 17 Aug, 2019 1 commit
-
-
Todd Volkert authored
We were using the `defaults` command-line utility to parse Plist files, but it was never supported by Apple, and it appears that in an upcoming OS release, it will be less likely to work: > WARNING: The defaults command will be changed in an upcoming > major release to only operate on preferences domains. General > plist manipulation utilities will be folded into a different > command-line program. Fixes https://github.com/flutter/flutter/issues/37701
-
- 10 Aug, 2019 1 commit
-
-
Jonah Williams authored
-
- 29 Jul, 2019 1 commit
-
-
Zachary Anderson authored
-
- 24 Jul, 2019 1 commit
-
-
Ian Hickson authored
-
- 19 Jul, 2019 1 commit
-
-
Jonah Williams authored
-
- 18 Jul, 2019 1 commit
-
-
Todd Volkert authored
This is a partial re-application of #24669, which was reverted due to Fuchsia breakages. https://github.com/flutter/flutter/issues/24413
-
- 16 Jul, 2019 1 commit
-
-
Todd Volkert authored
Slight cleanup of file locations in flutter_tools to make it easier to see which files are responsible for data reporting.
-
- 28 Jun, 2019 1 commit
-
-
Jonah Williams authored
-
- 26 Jun, 2019 1 commit
-
-
Lau Ching Jun authored
This allows us to override the behavior internally.
-
- 11 Jun, 2019 1 commit
-
- 08 Jun, 2019 2 commits
-
-
Jonah Williams authored
-
Ben Konyi authored
-
- 30 May, 2019 1 commit
-
-
Jason Simmons authored
This relands flutter/flutter#33163 with a fix to the integration_ui test.
-
- 22 May, 2019 2 commits
-
-
Jonah Williams authored
-
Ian Hickson authored
* Clean up some flutter_tools tests * Remove arbitrary retry that happens even for fundamental errors, and generally clean up _DevFSHttpWriter. * Update dependencies (requires fixes; see next commit) * Fixes for new dependencies.
-
- 16 May, 2019 1 commit
-
-
Alexandre Ardhuin authored
* use null aware operators * rollback changes about null-aware operator * disable lint prefer_is_not_empty
-
- 25 Apr, 2019 1 commit
-
-
Jonah Williams authored
-
- 08 Apr, 2019 1 commit
-
-
Jonah Williams authored
-
- 27 Mar, 2019 1 commit
-
-
Jonah Williams authored
-
- 19 Mar, 2019 1 commit
-
-
Priit Lätt authored
-
- 21 Feb, 2019 1 commit
-
-
Alexandre Ardhuin authored
-
- 01 Feb, 2019 1 commit
-
-
Jonah Williams authored
-
- 11 Nov, 2018 1 commit
-
-
Jonah Williams authored
-
- 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.
-