1. 21 Mar, 2019 1 commit
  2. 07 Mar, 2019 2 commits
  3. 06 Mar, 2019 1 commit
  4. 01 Mar, 2019 1 commit
    • Alexandre Ardhuin's avatar
      Add missing trailing commas (#28673) · 387f8854
      Alexandre Ardhuin authored
      * add trailing commas on list/map/parameters
      
      * add trailing commas on Invocation with nb of arg>1
      
      * add commas for widget containing widgets
      
      * add trailing commas if instantiation contains trailing comma
      
      * revert bad change
      387f8854
  5. 27 Feb, 2019 1 commit
  6. 15 Feb, 2019 1 commit
  7. 09 Feb, 2019 1 commit
  8. 06 Feb, 2019 1 commit
  9. 30 Jan, 2019 2 commits
  10. 29 Jan, 2019 1 commit
  11. 24 Jan, 2019 1 commit
  12. 21 Dec, 2018 1 commit
    • Pranay Airan's avatar
      Adding support for android app bundle - Issue #17829 (#24440) · 368cd7da
      Pranay Airan authored
      * adding support for android app bundle.
      
      * removing the debug statement.
      
      * fixing formatting and code review changes.
      
      * Revert "fixing formatting and code review changes."
      
      This reverts commit 2041d459f335242555a0b75e445343134c245494.
      
      * Fixing code formatting issues.
      
      * updating review comments fixing comments and spacing.
      
      * changing and to & to rerun the CI and tests.
      
      * updating the comment to re-run the test
      
      updating the comment to re-run the test
      
      * fixing the formatting.
      
      * updating comments to re-trigger build
      
      updating comments to re-trigger build
      368cd7da
  13. 10 Oct, 2018 1 commit
    • Greg Spencer's avatar
      Rename 'application' back to 'module', and make 'app' the default again for templates. (#22888) · 0ff9e8a9
      Greg Spencer authored
      We decided that redefining the default for templates was premature. We're going to go back to having "module" in experimental land again, and we'll try again when we have the feature set fully baked.
      
      This keeps the writing of the .metadata files, and writing the template type to them, because that was a good improvement, and there are still a bunch of added tests that improve our coverage.
      0ff9e8a9
  14. 04 Oct, 2018 2 commits
    • Greg Spencer's avatar
      Rename module --> application in flutter create command. (#22565) · 9f23866a
      Greg Spencer authored
      This renames the "module" template to the "application" template, and makes "application" the default. The existing "app" template is now deprecated.
      
      flutter create also now recognizes the type of project in an existing directory, and is able to recreate it without having the template type explicitly specified (although you can still do that). It does this now by first looking in the .metadata file for the new project_type field, and if it doesn't find that, then it looks at the directory structure. Also, the .metadata file is now overwritten even on an existing directory so that 1) the project_type can be added to legacy projects, and 2) the version of Flutter that updated the project last is updated.
      
      I also cleaned up a bunch of things in create_test.dart, added many more tests, and added an example test to the test/ directory in the generated output of the application template.
      
      Fixes #22530
      Fixes #22344
      9f23866a
    • Alexandre Ardhuin's avatar
      sort_constructors_first (#22575) · 2ea1d81c
      Alexandre Ardhuin authored
      2ea1d81c
  15. 01 Oct, 2018 1 commit
  16. 25 Sep, 2018 1 commit
    • Mikkel Nygaard Ravn's avatar
      Support materializing Flutter module host app on iOS (#21276) · a600fe7f
      Mikkel Nygaard Ravn authored
      * Prototype
      
      * Fix paths to Flutter library resources
      
      * Invoke pod install as necessary for materialized modules
      
      * Add devicelab test for module use on iOS
      
      * Remove debug output
      
      * Rebase, reame materialize editable
      
      * Add devicelab test editable iOS host app
      
      * Removed add2app test section
      a600fe7f
  17. 19 Sep, 2018 1 commit
  18. 18 Sep, 2018 3 commits
    • Chris Bracken's avatar
      Use Xcode legacy build system for iOS builds (#21901) (#21994) · f8c50ea1
      Chris Bracken authored
      Xcode 10 introduces a new build system which includes stricter checks on
      duplicate build outputs.
      
      When plugins are in use, there are two competing build actions that copy
      Flutter.framework into the build application Frameworks directory:
      
        1. The Embed Frameworks build phase for the Runner project
        2. The [CP] Embed Pods Frameworks build phase that pod install creates
           in the project.
      
      Item (1) is there to ensure the framework is copied into the built app
      in the case where there are no plugins (and therefore no CocoaPods
      integration in the Xcode project). Item (2) is there because Flutter's
      podspec declares Flutter.framework as a vended_framework, and CocoaPods
      automatically adds a copy step for each such vended_framework in the
      transitive closure of CocoaPods dependencies.
      
      As an immediate fix, we opt back into the build system used by Xcode 9
      and earlier. Longer term, we need to update our templates and
      flutter_tools to correctly handle this situation.
      
      See: https://github.com/flutter/flutter/issues/20685
      f8c50ea1
    • Chris Bracken's avatar
      Revert "Use Xcode legacy build system for iOS builds (#21901)" (#21966) · 4c045e79
      Chris Bracken authored
      This caused issues for projects without an Xcode workspace. Almost all
      Flutter projects in the wild will have a workspace, but this patch needs
      to add a check to catch any that lack one.
      
      This reverts commit 021f472e.
      4c045e79
    • Chris Bracken's avatar
      Use Xcode legacy build system for iOS builds (#21901) · 021f472e
      Chris Bracken authored
      Xcode 10 introduces a new build system which includes stricter checks on
      duplicate build outputs.
      
      When plugins are in use, there are two competing build actions that copy
      Flutter.framework into the build application Frameworks directory:
      
        1. The Embed Frameworks build phase for the Runner project
        2. The [CP] Embed Pods Frameworks build phase that pod install creates
           in the project.
      
      Item (1) is there to ensure the framework is copied into the built app
      in the case where there are no plugins (and therefore no CocoaPods
      integration in the Xcode project). Item (2) is there because Flutter's
      podspec declares Flutter.framework as a vended_framework, and CocoaPods
      automatically adds a copy step for each such vended_framework in the
      transitive closure of CocoaPods dependencies.
      
      As an immediate fix, we opt back into the build system used by Xcode 9
      and earlier. Longer term, we need to update our templates and
      flutter_tools to correctly handle this situation.
      
      See: https://github.com/flutter/flutter/issues/20685
      021f472e
  19. 12 Sep, 2018 1 commit
  20. 04 Sep, 2018 1 commit
  21. 31 Aug, 2018 1 commit
  22. 30 Aug, 2018 1 commit
  23. 16 Aug, 2018 1 commit
  24. 10 Aug, 2018 1 commit
  25. 07 Aug, 2018 1 commit
  26. 04 Aug, 2018 1 commit
  27. 03 Aug, 2018 2 commits
  28. 02 Aug, 2018 2 commits
  29. 23 Jul, 2018 1 commit
  30. 20 Jul, 2018 1 commit
  31. 16 Jul, 2018 2 commits
  32. 28 Jun, 2018 1 commit