1. 11 Sep, 2019 1 commit
  2. 06 Sep, 2019 1 commit
  3. 05 Sep, 2019 1 commit
  4. 03 Sep, 2019 2 commits
    • Harry Terkelsen's avatar
      Automatically generated registrants for web plugins (#39628) · d33cf115
      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
      d33cf115
    • Keerti Parthasarathy's avatar
      Update dartdoc to 0.28.5 (#39581) · 0ed3242a
      Keerti Parthasarathy authored
      0ed3242a
  5. 28 Aug, 2019 1 commit
  6. 23 Aug, 2019 1 commit
  7. 22 Aug, 2019 1 commit
  8. 21 Aug, 2019 1 commit
  9. 20 Aug, 2019 2 commits
  10. 15 Aug, 2019 4 commits
    • James Lin's avatar
      Update with more review feedback from jonahwilliams · 9823b3db
      James Lin authored
      * Remove the identity() function.
      * Make _flattenMap private.
      * Don't bother with ungrowable lists.
      9823b3db
    • James Lin's avatar
      Add assert messages · 4f3b7067
      James Lin authored
      4f3b7067
    • James Lin's avatar
      e3ffa768
    • James Lin's avatar
      Give `_runFlutterTest` the ability to validate command output · c02b805c
      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.
      c02b805c
  11. 12 Aug, 2019 1 commit
  12. 10 Aug, 2019 1 commit
  13. 09 Aug, 2019 1 commit
  14. 08 Aug, 2019 1 commit
  15. 06 Aug, 2019 3 commits
  16. 05 Aug, 2019 3 commits
  17. 02 Aug, 2019 1 commit
  18. 31 Jul, 2019 1 commit
  19. 29 Jul, 2019 1 commit
  20. 28 Jul, 2019 1 commit
  21. 26 Jul, 2019 1 commit
  22. 25 Jul, 2019 1 commit
  23. 24 Jul, 2019 1 commit
  24. 23 Jul, 2019 3 commits
    • Emmanuel Garcia's avatar
      Flutter build aar (#36732) · 242a4225
      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
          }
      }
      242a4225
    • Emmanuel Garcia's avatar
      Revert "Add flutter build aar (#35217)" (#36731) · c9b466f9
      Emmanuel Garcia authored
      This reverts commit 11460b83.
      c9b466f9
    • Emmanuel Garcia's avatar
      Add flutter build aar (#35217) · 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
          }
      }
      11460b83
  25. 22 Jul, 2019 3 commits
  26. 19 Jul, 2019 2 commits