07caa0fbfe
To support #61407 , the tool needs to check if a single widget reload is feasible, and then conditionally perform a fast reassemble. To accomplish this, the FlutterDevice class will have a WidgetCache injected. This will eventually contain the logic for parsing the invalidated dart script. Concurrent with the devFS update, the widget cache will be updated/checked if a single widget reload is feasible. If so, an expression evaluation with the target type is performed and the success is communicated through the devFS result. An integration test which demonstrates that this works is already present in https://github.com/flutter/flutter/blob/master/packages/flutter_tools/test/integration.shard/hot_reload_test.dart#L86 Finally, when actually performing the reassemble the tool simply checks if this flag has been set and calls the alternative reassemble method. Cleanups: Remove modules, as this is unused now.
Flutter Tools
This section of the Flutter repository contains the 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. Further, familiarize yourself with the style guide, which we follow.
Setting up
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 the Tool
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.
Running the analyzer
To run the analyzer on Flutter Tools, in this directory run:
$ ../../bin/flutter analyze
Writing tests
As with other parts of the Flutter repository, all changes in behavior must be
tested.
Tests live under the test/ subdirectory.
- Hermetic unit tests of tool internals go under
test/general.shard. - Tests of tool commands go under
test/commands.shard. Hermetic tests go under itshermetic/subdirectory. Non-hermetic tests go under itspermeablesub-directory. - Integration tests (e.g. tests that run the tool in a subprocess) go under
test/integration.shard.
In general, the tests for the code in a file called file.dart should go in a
file called file_test.dart in the subdirectory that matches the behavior of
the test.
We measure test coverage post-submit. A change that deletes code might decrease test coverage, however most changes that add new code should aim to increase coverage. In particular the coverage of the diff should be close to the average coverage, and should ideally be better.
Running the tests
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
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