Obviously this will require an e-mail and so forth.

Fixes #2343

It might be valuable to have a period of time where the tool accepts both kinds. For example, it could look at pubspec.yaml first and look for flutter.yaml if it doesn't find the flutter key. (If it does find the flutter key, it should verify that flutter.yaml doesn't exist.

Also, consider a message in the case where it falls back to flutter.yaml explaining how to transition to the new location.

Transitioning is really simple. How about just detecting the flutter.yaml file and saying what to do if it exists? (Rather than actually parsing both, which would require multiple schemas, etc.)

ok

I have added a check for flutter.yaml files that gets triggered for the same commands that previously checked for a pubspec.yaml file, along with a multiparagraph precise step-by-step explanation for what to do and a pointer to an example. PTAL. :-)

I'll merge this while I'm at the office so that I can provide better support to anyone it breaks.

I'll post the following e-mail when I do so:

flutter.yaml merging into pubspec.yaml

The next time you update your Flutter repository, you will find that you need to make a change: you will need to merge your flutter.yaml file into your pubspec.yaml file and then delete your flutter.yaml file.

Just running "flutter run" will give you detailed instructions on how to do this, or you can contact me and I'll help you out.

This is part of an attempt to simplify the Flutter development experience by having fewer files to deal with.

Woot, happy to see this being fixed!

@devoncarew @pq do we use the presence of a flutter.yaml file for anything in IJ?

@mit-mit: 👍 => flutter/flutter-intellij#656