- 10 Oct, 2018 1 commit
-
-
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.
-
- 04 Oct, 2018 1 commit
-
-
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
-
- 19 May, 2017 1 commit
-
-
Brian Slesinsky authored
IDEA users sometimes want to create multiple Flutter modules in the same IDEA project. See discussion: https://github.com/flutter/flutter-intellij/issues/1014 In this case, we will actually have pairs of modules, one for Flutter and one for Android. Renaming the android module to make the relationship obvious. But, don't delete the old file yet to avoid breaking existing users. We can do that after the next Flutter plugin release.
-
- 14 Apr, 2017 1 commit
-
-
Brian Slesinsky authored
Generates an android.iml file and a package-level library for flutter.jar. Does not set up an Android SDK in IDEA; this isn't possible with a template-based approach. But IDEA shows a clear warning, so the user can fix this by setting the SDK. (When creating a Flutter project from within IDEA, we can fix this up afterwards in the plugin.)
-
- 30 Mar, 2017 1 commit
-
-
Michael Thomsen authored
-
- 14 Feb, 2017 1 commit
-
-
Michael Thomsen authored
* Move .iml file back to project root directory * Update .iml location in all examples
-
- 23 Jan, 2017 1 commit
-
-
Michael Thomsen authored
* Disable 'Show Excluded' by default * Move .iml file inside .idea dir * Remove pub and build excludions as they are automatically set by the Dart plugin * Exclude .idea folder (new users will edit it through the IJ UI, not the file) * Move .iml files into .idea dir to be consistent with template changes * Add workspace.xml from new template to existing samples * Update current examples to match template changes for excluding folders * Add missing flutter.yaml to make sure there are no analysis errors * Add back .pub and build excludeFolder tags per https://github.com/flutter/flutter-intellij/issues/630#issuecomment-272887230 * Remove workspace.xml from example per review feedback
-
- 20 Oct, 2016 1 commit
-
-
Devon Carew authored
-