[Feature Request] Add support for multiple flutter project directories

[vanlooverenkoen]

Is your feature request related to a problem? Please describe.
First of all, I want to say thanks for your amazing work!!!!

We are using fvm for all our projects. And we are also using your mac GUI tool.

For that we were thinking about another feature for the GUI tool.
I use our macbook at work and at home. To split up our work and personal projects in a separate directory. Right now we can only select 1 directory.

Describe the solution you'd like
It would be nice to have an option to add multiple directories.

[leoafarias]

@vanlooverenkoen Thanks for the suggestion. I have some questions.

• I assume those directories are also not nested under a directory that can be added, is that correct?
• With that do see the need to categorize the projects for those directories differently, for filtering?

[vanlooverenkoen]

In my case. My folder structure is like this:

~/Documents/work/*
~/Documents/personal-projects/
EXTERNAL_DRIVE/archive-projects/

I think it would be nice to have filtering and categories as well but I think that can be an extra feature on top of this one.

[leoafarias]

If you select Documents as the folder you should be able to get work, and personal projects. It might take a bit longer for the initial load, but after that the paths are cached.

For the external_drive this would not work.

[vanlooverenkoen]

Alright. for now I am indeed using Documents

[leoafarias]

@vanlooverenkoen I will leave this open and add it to the backlog. Will look over to see if there is an easy way to implement this that does not complicate the simple case.

[s0nerik]

Want to point out that at the moment fvm is hard to use for modular Flutter projects.

For example, even in a quite simple case (with not that many modules) like the one below, calling fvm flutter --version inside the project root and client_app would result in different versions being printed since none of the sub-projects have their own .fvm directory. The first one will print a proper project-level flutter version while the second one will print the global default flutter version.

A real-life example of a (somewhat) modular project structure (none of the sub-projects have .fvm directory):

I believe that it won't be hard to make fvm look for the ./fvm/flutter_sdk not only within the current directory but also within some N levels of parent directories.

This would allow for a neat flutter version scoping that, in turn, will make both the issue's case and modular project cases work well.

@leoafarias Do you see any caveats in the algorithm explained above?

[leoafarias]

Released on version 0.0.8. However, instead of providing the root directory of your projects, it just allows adding the project implicitly