- 14 Feb, 2017 1 commit
-
-
Michael Goderbauer authored
-
- 13 Feb, 2017 1 commit
-
-
Todd Volkert authored
-
- 27 Jan, 2017 3 commits
-
-
Ian Hickson authored
Move the drive/run common stuff to RunCommandBase, rather than the superclass which applies to everything. Implement --no-resident (fixes https://github.com/flutter/flutter/issues/5448). This is particularly useful when running flutter from scripts. Rename RunAndStayResident to ColdRunner.
-
Ian Hickson authored
...for the port arguments
-
Ian Hickson authored
...and add --diagnostic-port. ...and document port 0.
-
- 26 Jan, 2017 2 commits
-
-
xster authored
* Add a check in case the flutter directory in .packages no longer exists. Clean up and prompt user * Update documentation to use flutter packages get for end-users instead of flutter update-packages. * Merge missing sdk error with the multiple sdk error. They're really the same thing. * Use flutterPath in both checks. * Change file_system’s copy folder to copy director which takes into account the file system * Test support files * Add test and split into 2 messages again. * Move tests to run in memory file system's copy. Tested with dev/bots/test.sh
-
Todd Volkert authored
-
- 24 Jan, 2017 1 commit
-
-
Ian Hickson authored
-
- 23 Jan, 2017 1 commit
-
-
Todd Volkert authored
-
- 22 Jan, 2017 1 commit
-
-
Ian Hickson authored
-
- 09 Jan, 2017 1 commit
-
-
Todd Volkert authored
This ensures that accidental usages of dart:io's file API don't creep in over time.
-
- 07 Jan, 2017 1 commit
-
-
Todd Volkert authored
This removes direct file access from within flutter_tools in favor of using `package:file` via a `FileSystem` that's accessed via the `ApplicationContext`. This lays the groundwork for us to be able to easily swap out the underlying file system when running Flutter tools, which will be used to provide a record/replay file system, analogous to what we have for process invocations.
-
- 19 Dec, 2016 1 commit
-
-
Devon Carew authored
-
- 06 Dec, 2016 1 commit
-
-
Todd Volkert authored
This argument will enable mocking of os-layer process invocations, where the mock behavior will come from replaying a previously- recorded set of invocations. At the point of process invocation, the key metadata for the invocation will be looked up in the recording's manifest, and iff a matching record exists in the manifest, the process will be mocked out with data derived from the corresponding recorded process (e.g. stdout, stderr, exit code).
-
- 02 Dec, 2016 1 commit
-
-
Todd Volkert authored
* Add --record-to option to flutter tools This option will cause flutter tools to record all process invocations that occur and serialize their stdout and stderr to files that get added to a "recording" ZIP file. This is part of an effort to be able to test flutter tools in a hermetic environment. As a side-benefit, this recording should prove an excellent attachment to any bug report.
-
- 29 Nov, 2016 2 commits
-
-
John McCutchan authored
-
John McCutchan authored
-
- 14 Nov, 2016 2 commits
-
-
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
-
Dan Rubel authored
* convert pubGet to throw ToolExit on non-zero exit code * convert commandValidator to throw ToolExit for non-zero exit code * convert flutter commands to throw ToolExit for non-zero exit code * use convenience method throwToolExit * only show "if this problem persists" for unusual exceptions
-
- 01 Nov, 2016 1 commit
-
-
Adam Barth authored
Fixes #6417
-
- 21 Oct, 2016 1 commit
-
-
Jason Simmons authored
With the old policy the most recent log would not be printed until the next log is produced (which may be indefinitely). This change prints logs immediately along with a time delta since the previous log.
-
- 28 Sep, 2016 1 commit
-
-
John McCutchan authored
When using --use-application-binary: - [x] Stop flutter run from checking for a pubspec.yaml in current directory - [x] Stop flutter run from invoking pub get - [x] Set 'shouldBuild' based on --use-application-binary - [x] Stop requiring 'lib/main.dart' to be present before running. - [x] Stop building an FLX when launching on Android
-
- 22 Sep, 2016 2 commits
- 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
-
- 08 Sep, 2016 1 commit
-
-
Dan Rubel authored
When flutter run is used on a Mac and no devices are specified or attached, suggest launching a simulator first. Fixes https://github.com/flutter/flutter/issues/5674
-
- 01 Sep, 2016 1 commit
-
-
Dan Rubel authored
* improve device matching error message fixes https://github.com/flutter/flutter/issues/5675
-
- 23 Aug, 2016 1 commit
-
-
Todd Volkert authored
-
- 19 Aug, 2016 1 commit
-
-
Jason Simmons authored
Do not throw when resolving a local engine if the .packages map does not include the flutter package (#5519)
-
- 16 Aug, 2016 1 commit
-
-
Devon Carew authored
* update the cache earlier * add documentation
-
- 09 Aug, 2016 1 commit
-
-
Devon Carew authored
* make flutter run work with a pre-built apk * refactor to remove the buildDir param
-
- 27 Jul, 2016 1 commit
-
-
pq authored
-
- 25 Jul, 2016 3 commits
-
-
Devon Carew authored
* This reverts commit 5e7e7b6e. * default to lib/main.dart
-
Devon Carew authored
This reverts commit 32ad81c8.
-
Devon Carew authored
-
- 30 Jun, 2016 1 commit
-
-
Adam Barth authored
It can cause trouble if the user has a newer Android SDK installed normally. Instead, just use the normal Android SDK.
-
- 15 Jun, 2016 1 commit
-
-
Ian Hickson authored
* Fix `flutter upgrade` * Fix builds on iOS
-
- 14 Jun, 2016 3 commits
-
-
Ian Hickson authored
-
Ian Hickson authored
This prevents multiple simultaneous runs of the analyzer from stomping over each other (e.g. multiple runs of 'update-packages'). Certain long-lived commands (like analyze, run, logs) are exempted once they've done enough work to be safe from most stomping action. This still doesn't make us entirely safe from craziness, e.g. if you're half way through an 'update-packages' run and you call 'git pull', who knows what state you'll end up in. But there's only so much one can do. Fixes https://github.com/flutter/flutter/issues/2762
-
Ian Hickson authored
-