- 05 Oct, 2018 1 commit
-
-
Alexandre Ardhuin authored
-
- 26 Sep, 2017 1 commit
-
-
Todd Volkert authored
This makes command validation happen as part of `verifyThenRunCommand()`, using a newly introduced protected method (`validateCommand()`) rather than a `commandValidator` property (that subclasses were responsible for manually invoking).
-
- 29 Jun, 2017 1 commit
-
-
Mikkel Nygaard Ravn authored
-
- 26 Apr, 2017 1 commit
-
-
Todd Volkert authored
`adb` can sometimes hang, which will in turn hang the Dart isolate if we're using `Process.runSync()`. This changes many of the `Device` methods to return `Future<T>` in order to allow them to use the async process methods. A future change will add timeouts to the associated calls so that we can properly alert the user to the hung `adb` process. This is work towards #7102, #9567
-
- 10 Mar, 2017 1 commit
-
-
Todd Volkert authored
* Rename `Device.platform` to `Device.targetPlatform` to avoid collision with the exported variable from `platform.dart`
-
- 04 Mar, 2017 1 commit
-
-
Chris Bracken authored
-
- 14 Nov, 2016 1 commit
-
-
Dan Rubel authored
* Remove the workaround that pinned args to v0.13.6 This reverts most of the changes in commit 6331b6c8 * throw exception if exit code is not an integer * rework command infrastructure to throw ToolExit when non-zero exitCode * convert commands to return Future<Null> * cleanup remaining commands to use throwToolExit for non-zero exit code * remove isUnusual exception message * add type annotations for updated args package
-
- 16 Sep, 2016 1 commit
-
-
Dan Rubel authored
* refactor _run to runCmd * replace requiresProjectRoot getter with call to commandValidator * replace requiresDevice getter with call to findTargetDevice * trace command requires a debug connection, not a device * inline androidOnly getter * rename command methods to verifyTheRunCmd and runCmd * move common verification into BuildSubCommand * rename deviceForCommand to device * rename methods to verifyThenRunCommand and runCommand
-
- 07 Jun, 2016 1 commit
-
-
Devon Carew authored
* refactor the --resident run option into a separate file * update daemon to run --resident apps * re-plumbing daemon start * send app logs * update tests * review changes * fix test runner * remove PackageMap.createGlobalInstance; rely on the ctor * review comments
-
- 04 Apr, 2016 1 commit
-
-
Devon Carew authored
-
- 14 Mar, 2016 1 commit
-
-
Hixie authored
-
- 03 Mar, 2016 1 commit
-
-
Devon Carew authored
-
- 26 Feb, 2016 1 commit
-
-
Devon Carew authored
-
- 21 Jan, 2016 1 commit
-
-
Devon Carew authored
-
- 29 Nov, 2015 1 commit
-
-
Adam Barth authored
1) Moved basic utility code into base/ directory to make it clear which code doesn't depend on Flutter-specific knowldge. 2) Move the CommandRunner subclasses into a runner/ directory because these aren't commands themselves.
-
- 10 Nov, 2015 1 commit
-
-
Adam Barth authored
-
- 29 Oct, 2015 1 commit
-
-
Devon Carew authored
remove an unused import review comments rename st --> stack
-
- 12 Oct, 2015 2 commits
-
-
Adam Barth authored
This patch makes `flutter start` work without a clone of the engine git repository. Making this work pulled a relatively large refactor of how the commands interact with application packages and devices. Now commands that want to interact with application packages or devices inherit from a common base class that holds stores of those objects as members. In production, the commands download and connect to devices based on the build configuration stored on the FlutterCommandRunner. In testing, these fields are used to mock out the real application package and devices.
-
Ian Fischer authored
Also fixes some minor bugs with iOS and Android interactions.
-
- 10 Oct, 2015 1 commit
-
-
Adam Barth authored
I'm trying to get a feel for the code by writing some simple cleanup patches.
-
- 07 Oct, 2015 1 commit
-
-
Ian Fischer authored
-
- 06 Oct, 2015 1 commit
-
-
Devon Carew authored
-
- 25 Sep, 2015 1 commit
-
-
Ian Fischer authored
-