History

Restructure ProjectFileInvalidator.findInvalidated a bit (#42008 )

Restructure ProjectFileInvalidator.findInvalidated a bit

I plan to modify `ProjectFileInvalidator.findInvalidated` to allow
it to use `FileStat.stat` instead of `FileStat.statSync`.
Restructure `findInvalidated` a bit so that `FileStat.statSync` is
called in only one place.

Note that this change now always counts the `.packages` file as one
of the files scanned, even if it does not exist.  I think that this
is okay since it more accurately reflects the number of times that we
hit the filesystem with `stat()`, and it is consistent with how other
files are counted.

2019-10-04 17:22:35 -07:00

bin

AOT support for Linux Desktop I: switch Linux builds to assemble (#41612 )

2019-10-04 12:13:36 -07:00

doc

Add emulatorID field to devices in daemon (#34794 )

2019-06-26 16:39:23 +01:00

gradle

Use mergeResourcesProvider instead of deprecated mergeResources (#41942 )

2019-10-03 20:42:43 -07:00

ide_templates/intellij

Add actions and keyboard shortcut map support (#33298 )

2019-06-04 11:30:24 -07:00

lib

Restructure ProjectFileInvalidator.findInvalidated a bit (#42008 )

2019-10-04 17:22:35 -07:00

schema

Add the beginnings of plugin support for Windows and Linux (#41015 )

2019-09-26 14:01:57 -07:00

static

Reland support flutter test on platform chrome (#33859 )

2019-06-05 15:27:49 -07:00

templates

Generate projects using the new Android embedding (#41666 )

2019-10-04 06:23:03 -07:00

test

Clean up ProjectFileInvalidator.findInvalidated a bit (#41889 )

2019-10-04 12:55:17 -07:00

tool

indent formal parameters correctly (#41644 )

2019-10-04 11:00:18 +02:00

analysis_options.yaml

[flutter_tool] Use curly braces around single statment control structures (#40446 )

2019-09-13 14:51:35 -07:00

BUILD.gn

Add "web" server device to allow running flutter for web on arbitrary browsers (#39951 )

2019-09-10 19:29:31 -07:00

build.yaml

Reland support flutter test on platform chrome (#33859 )

2019-06-05 15:27:49 -07:00

dart_test.yaml

use pub run for create test and remove [INFO] logs (#35839 )

2019-07-10 08:48:01 -07:00

pubspec.yaml

Revert "replace package:vm_service_client with package:vm_service in the devicelab project (#41646 )" (#41960 )

2019-10-03 21:30:37 -07:00

README.md

[flutter_tool] Add some useful commands to the README.md (#36560 )

2019-07-23 09:47:06 -07:00

README.md

Flutter Tools

Command line developer tools for building Flutter applications.

Working on Flutter Tools

Be sure to follow the instructions on CONTRIBUTING.md to set up your development environment.

Setup

First, ensure that the Dart SDK and other necessary artifacts are available by invoking the Flutter Tools wrapper script. In this directory run:

$ ../../bin/flutter --version

Running

To run Flutter Tools from source, in this directory run:

$ ../../bin/cache/dart-sdk/bin/dart bin/flutter_tools.dart

followed by command line arguments, as usual.

Analyzing

To run the analyzer on Flutter Tools, in this directory run:

$ ../../bin/flutter analyze

Testing

To run the tests in the test/ directory, first ensure that there are no connected devices. Then, in this directory run:

$ ../../bin/cache/dart-sdk/bin/pub run test

The tests in test/integration.shard are slower to run than the tests in test/general.shard. To run only the tests in test/general.shard, in this directory run:

$ ../../bin/cache/dart-sdk/bin/pub run test test/general.shard

To run the tests in a specific file, run:

$ ../../bin/cache/dart-sdk/bin/pub run test test/general.shard/utils_test.dart

When running all of the tests, it is a bit faster to use build_runner. First, set FLUTTER_ROOT to the root of your Flutter checkout. Then, in this directory run:

$ ../../bin/cache/dart-sdk/bin/pub run build_runner test

Forcing snapshot regeneration

To force the Flutter Tools snapshot to be regenerated, delete the following files:

$ rm ../../bin/cache/flutter_tools.stamp ../../bin/cache/flutter_tools.snapshot