- 11 Sep, 2019 1 commit
-
-
Emmanuel Garcia authored
-
- 06 Sep, 2019 1 commit
-
-
Jonah Williams authored
-
- 05 Sep, 2019 1 commit
-
-
Devon Carew authored
-
- 03 Sep, 2019 2 commits
-
-
Harry Terkelsen authored
* WIP on web plugin registry * WIP on registering plugins * WIP on web plugin registration * Only generate `package:flutter_web_plugins` imports if plugins are defined * Add parsing test * Add documentation * Fix analyzer warnings * add license headers * Add tests for package:flutter_web_plugins * Run `flutter update-packages --force-upgrade` * Fix analyzer errors * Fix analyzer error in test * Update copyright and remove flutter SDK constraints * Enable tests since engine has rolled * add flutter_web_plugins tests to bots * Create an empty .packages file for WebFs test
-
Keerti Parthasarathy authored
-
- 28 Aug, 2019 1 commit
-
-
Michael Goderbauer authored
-
- 23 Aug, 2019 1 commit
-
-
Yegor authored
* shard tests * make foundation tests pass
-
- 22 Aug, 2019 1 commit
-
-
Chris Bracken authored
This fixes a breakage in fuchsia where package_config version 1.1.0 is required but flutter_tools is currently locked to 1.05.
-
- 21 Aug, 2019 1 commit
-
-
∂ω∂ authored
-
- 20 Aug, 2019 2 commits
-
-
Ian Hickson authored
-
James D. Lin authored
Flutter widget tests assert if a test completes with timers still pending. However, it can be hard to diagnose where a pending timer came from. For example, a widget might consume a third-party library that internally uses a timer. I added a FakeAsync.pendingTimersDebugInfo getter to quiver (https://github.com/google/quiver-dart/pull/500). Make flutter_test use it. Additionally modify Flutter's debugPrintStack to take an optional StackTrace argument instead of always printing StackTrace.current. Fixes #4237.
-
- 15 Aug, 2019 4 commits
-
-
James Lin authored
* Remove the identity() function. * Make _flattenMap private. * Don't bother with ungrowable lists.
-
James Lin authored
-
James Lin authored
-
James Lin authored
In another change (#37646), I want to test that a test fails and prints expected output. I didn't see an existing way to do that, so I modified `_runFlutterTest` and `runCommand` to allow capturing the output. Currently capturing and printing output are mutually exclusive since we don't need both. Some awkward bits: * There already exists a `runAndGetStdout` function that is very similar to `runCommand`, and this change makes the conceptual distinction more confusing. * `runFlutterTest` has multiple code paths for different configurations. I don't understand what the different paths are for, and I added output checking only along one of them.
-
- 12 Aug, 2019 1 commit
-
-
James Lin authored
-
- 10 Aug, 2019 1 commit
-
-
Emmanuel Garcia authored
-
- 09 Aug, 2019 1 commit
-
-
Yegor authored
update dependencies; add a Web smoke test
-
- 08 Aug, 2019 1 commit
-
-
Dan Field authored
-
- 06 Aug, 2019 3 commits
-
-
Dan Field authored
-
Emmanuel Garcia authored
- 05 Aug, 2019 3 commits
-
-
Jonah Williams authored
-
Jonah Williams authored
-
Jonah Williams authored
-
- 02 Aug, 2019 1 commit
-
-
Jenn Magder authored
-
- 31 Jul, 2019 1 commit
-
-
Keerti Parthasarathy authored
-
- 29 Jul, 2019 1 commit
-
-
Emmanuel Garcia authored
Fixes these issues: #30916 #34089 #36479 #29648
-
- 28 Jul, 2019 1 commit
-
-
Kate Lovett authored
-
- 26 Jul, 2019 1 commit
-
-
Michael Klimushyn authored
* Roll back the AAR build experiment This has been breaking flutter/plugins CI for the past day. * Remove integration tests that rely on the AAR flag
-
- 25 Jul, 2019 1 commit
-
-
Emmanuel Garcia authored
Fixes #36817
-
- 24 Jul, 2019 1 commit
-
-
Matt Carroll authored
-
- 23 Jul, 2019 3 commits
-
-
Emmanuel Garcia authored
`flutter build aar` This new build command works just like `flutter build apk` or `flutter build appbundle`, but for plugin and module projects. This PR also refactors how plugins are included in app or module projects. By building the plugins as AARs, the Android Gradle plugin is able to use Jetifier to translate support libraries into AndroidX libraries for all the plugin's native code. Thus, reducing the error rate when using AndroidX in apps. This change also allows to build modules as AARs, so developers can take these artifacts and distribute them along with the native host app without the need of the Flutter tool. This is a requirement for add to app. `flutter build aar` generates POM artifacts (XML files) which contain metadata about the native dependencies used by the plugin. This allows Gradle to resolve dependencies at the app level. The result of this new build command is a single build/outputs/repo, the local repository that contains all the generated AARs and POM files. In a Flutter app project, this local repo is used by the Flutter Gradle plugin to resolve the plugin dependencies. In add to app case, the developer needs to configure the local repo and the dependency manually in `build.gradle`: repositories { maven { url "<path-to-flutter-module>build/host/outputs/repo" } } dependencies { implementation("<package-name>:flutter_<build-mode>:1.0@aar") { transitive = true } }
-
Emmanuel Garcia authored
This reverts commit 11460b83.
-
Emmanuel Garcia authored
`flutter build aar` This new build command works just like `flutter build apk` or `flutter build appbundle`, but for plugin and module projects. This PR also refactors how plugins are included in app or module projects. By building the plugins as AARs, the Android Gradle plugin is able to use Jetifier to translate support libraries into AndroidX libraries for all the plugin's native code. Thus, reducing the error rate when using AndroidX in apps. This change also allows to build modules as AARs, so developers can take these artifacts and distribute them along with the native host app without the need of the Flutter tool. This is a requirement for add to app. `flutter build aar` generates POM artifacts (XML files) which contain metadata about the native dependencies used by the plugin. This allows Gradle to resolve dependencies at the app level. The result of this new build command is a single build/outputs/repo, the local repository that contains all the generated AARs and POM files. In a Flutter app project, this local repo is used by the Flutter Gradle plugin to resolve the plugin dependencies. In add to app case, the developer needs to configure the local repo and the dependency manually in `build.gradle`: repositories { maven { url "<path-to-flutter-module>build/host/outputs/repo" } } dependencies { implementation("<package-name>:flutter_<build-mode>:1.0@aar") { transitive = true } }
-
- 22 Jul, 2019 3 commits
-
-
Jonah Williams authored
-
Jonah Williams authored
This reverts commit bd52a78c.
-
Jonah Williams authored
-
- 19 Jul, 2019 2 commits
-
-
Kate Lovett authored
-
Todd Volkert authored
-