Version matching strategy? about flutter_everywhere

[rodydavis]

Absolutely, I’ll update the readme!

[rodydavis]

I think this project will target the master branch and flutter version releases.

[stuartmorgan]

I recommend that you prominently document that limitation, and include the hash of Flutter that your latest sync from FDE is matched with in the README so that people know how to get a version that is likely to work.

I see from project history that you've updated from FDE several times, but still aren't including this info in the readme. Given that I'm assuming that I misunderstood and this is intended primarily for your use, where knowing the necessary versions to match isn't an issue. Given that, closing.

[rodydavis]

@stuartmorgan yes I am using it for all my stuff. I was trying to create releases that matched the Flutter version.

I’ll update the documentation but right now I am personally using it and updating from the various sources and fixing any limitations.

I target the master and dev branch of Flutter.

I use this project to populate my examples and other Flutter apps that I need to support desktop.

I want to reduce the amount of boilerplate to get up and running.