1. 08 Feb, 2024 1 commit
  2. 04 Feb, 2024 2 commits
  3. 09 Nov, 2023 1 commit
  4. 03 Nov, 2023 1 commit
  5. 02 Nov, 2023 1 commit
  6. 12 Apr, 2023 1 commit
  7. 11 Apr, 2023 1 commit
  8. 29 Mar, 2023 1 commit
  9. 15 Oct, 2021 1 commit
  10. 20 Apr, 2021 1 commit
  11. 02 Dec, 2020 1 commit
  12. 23 Nov, 2020 1 commit
  13. 20 Nov, 2020 1 commit
  14. 11 Aug, 2020 1 commit
  15. 10 Aug, 2020 1 commit
  16. 04 Aug, 2020 2 commits
  17. 13 Feb, 2020 1 commit
  18. 27 Nov, 2019 1 commit
    • Ian Hickson's avatar
      License update (#45373) · 449f4a66
      Ian Hickson authored
      * Update project.pbxproj files to say Flutter rather than Chromium
      
      Also, the templates now have an empty organization so that we don't cause people to give their apps a Flutter copyright.
      
      * Update the copyright notice checker to require a standard notice on all files
      
      * Update copyrights on Dart files. (This was a mechanical commit.)
      
      * Fix weird license headers on Dart files that deviate from our conventions; relicense Shrine.
      
      Some were already marked "The Flutter Authors", not clear why. Their
      dates have been normalized. Some were missing the blank line after the
      license. Some were randomly different in trivial ways for no apparent
      reason (e.g. missing the trailing period).
      
      * Clean up the copyrights in non-Dart files. (Manual edits.)
      
      Also, make sure templates don't have copyrights.
      
      * Fix some more ORGANIZATIONNAMEs
      449f4a66
  19. 25 Sep, 2019 1 commit
  20. 03 Jul, 2019 1 commit
  21. 19 Jan, 2019 2 commits
  22. 18 Dec, 2018 1 commit
  23. 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
  24. 28 Jul, 2018 1 commit
    • Greg Spencer's avatar
      Fix the gradle templates so that they default to values rather than throw... · e262817a
      Greg Spencer authored
      Fix the gradle templates so that they default to values rather than throw build exceptions. (#19916)
      
      When creating a new project, the build fails with an error similar to:
      
      "versionCode not found. Define flutter.versionCode in the local.properties file."
      
      This puts developers in the untenable situation of having to edit a file with local paths, but being unable to check it in.
      
      This changes the templates to default to using versionCode 1 and version "1.0" if they are not defined in the local.properties file.
      
      Fixes #18983.
      e262817a
  25. 01 Jun, 2018 1 commit
  26. 31 May, 2018 2 commits
  27. 30 May, 2018 1 commit
    • Ralph Bergmann's avatar
      add version to pubspec.yaml (#16857) · c65e9d19
      Ralph Bergmann authored
      Uses the `version` property from the `pubspec.yaml` file to set the corresponding fields in the `local.properties` file respectively in the `Generated.xcconfig` file.
      
      The `--build-name` and `--build-number` options have changed. Now they trump the `version` property from the `pubspec.yaml` file.
      
      If the `version` property is not set and the  `--build-name` and `--build-number` options are not provided, the build command will not change the `local.properties` / `Generated.xcconfig` file.
      c65e9d19
  28. 28 May, 2018 4 commits
  29. 08 Jan, 2018 2 commits
  30. 14 Dec, 2017 1 commit
  31. 13 Dec, 2017 1 commit
  32. 29 Jun, 2017 1 commit