Survey code to determine scope of breaking project root assumption

[stevemessick]

We have a few requests that the Flutter project root directory be separated from the IntelliJ project directory. Actually, I think IntelliJ considers a project to be a collection of modules, independent of their location. That is, the modules do not have to share a common parent directory. One example is #5150.

We need to survey the code base to find where we assume the Flutter project root is the top-level directory in the project.

[shinayser]

Hope this get's fixed soon. Flutter projects are starting to become more complex every day and the necessity of a multi module support on the tooling side is a must. Here is a example of a problem I found when trying to perform tests on multi module projects: #5388 (comment)

[benoitskipr]

one of the assumptions seems to be the option to open Xcode from the right-click menu.
on monorepos, it always opens the first flutter project/module, disregarding the one we've actually right-clicked on.
and as it's not very clear in xcode, you can lose quite some time until you figure out you're in the wrong project.
making the 'open in xcode' option worthless, because you then have to open the right project manually inside xcode.

[krispykalsi]

I solved #5388 by adding each package directory as a content root. Here's how to do it (works on v2021.3) -

Source
Also, make sure to remove the parent directory as a content root before adding the child directories as one.