1. 22 Apr, 2021 1 commit
  2. 02 Dec, 2020 1 commit
  3. 23 Nov, 2020 1 commit
  4. 20 Nov, 2020 1 commit
  5. 14 Sep, 2019 1 commit
  6. 20 Oct, 2018 1 commit
  7. 18 Oct, 2018 2 commits
  8. 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
  9. 04 Oct, 2018 1 commit
    • 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
  10. 30 Aug, 2018 1 commit
  11. 16 Aug, 2018 1 commit
  12. 02 Jul, 2018 1 commit
  13. 22 Jun, 2018 1 commit
  14. 01 Jun, 2018 1 commit
  15. 31 May, 2018 2 commits
  16. 28 May, 2018 4 commits
  17. 06 Jan, 2018 1 commit
  18. 04 Jan, 2018 2 commits
  19. 03 Jan, 2018 2 commits
  20. 14 Dec, 2017 2 commits
  21. 29 Jun, 2017 1 commit
  22. 20 Jun, 2017 1 commit
  23. 27 Apr, 2017 1 commit
  24. 04 Apr, 2017 1 commit
    • Jakob Andersen's avatar
      Android: Set evaluationDependsOn for plugin subprojects. (#9179) · 5541d71b
      Jakob Andersen authored
      Gradle projects are evaluated in lexicographical order, and the plugin
      projects are at the same level as the :app project, so if a plugin has
      a name that comes before 'app' (like, for example, any name that starts
      with a capital letter), the plugin project will be evaluated before
      :app.
      
      Since :app applies the Flutter Gradle plugin, which tries to
      modify the dependencies of the plugin projects, we have a problem if the
      plugin projects have already been evaluated. Adding
      evaluationDependsOn(':app') to the plugin projects fixes this.
      
      Updated example projects to the latest (plugin-enabled) Gradle build
      files.
      
      Also removed two unused imports in `pluginClass.java.tmpl`.
      5541d71b
  25. 21 Feb, 2017 1 commit
  26. 23 Jan, 2017 1 commit
  27. 15 Dec, 2016 1 commit
  28. 03 Jun, 2016 1 commit
  29. 10 May, 2016 1 commit
  30. 14 Mar, 2016 1 commit