[FEATURE] Multi-Project support

[alpox]

Often times when working on PHP Projects I am jumping from one to another without closing neovim. In addition, the root path of the Symfony project is often a different one from the PWD (Usually PWD is higher up as we have monorepos with frontend/backend etc. in it and my PWD is in the root).

Given that the root detection for the vendor folder and the container xml happens currently on start of Neovim, it looks like this kind of workflow is currently not supported.

[shinyvision]

Hi Alpox

Yes, this would be possible. It would require some refactoring, though, because currently the LSP only keeps track of 1 container config and autoload etc per instance. But it should be possible to map different project roots in a single cwd instance, given that it has vendor/composer and var/cache/dev/App_KernelDevDebugContainer.xml in the closest parent-traversing path.

Hmm, maybe for now you can work around the issue by running 2 instances of Neovim, each in their own directory inside of the monorepo? That is what I do myself with different tmux sessions per project, but in my work I really never use large monorepos.

PS. If you build from source, you should be able to get parsing of multiple container xmls to work. I needed that for Sulu projects to work correctly. Maybe that's useful for you, too.