Mathew Attlee

I guess it could be possible to have an option to manually override the path it checks for package.json but in this case are you staying there are multiple ones,...

Yes but there will be package.json in people's vendor directories

Now I am working on a project with mono repo I can see the problem but I don't see this a problem specifically with vim-test but any plugin that assumes...

Interesting, so projectionist let's you define multiple projects and `call projectionist#path()` will give you the project root path for that file?

> @codeinabox Given this project already uses projectionist, maybe it should use the result of the function call `call projectionist#path()` as the project dir for a file? @janko do think...

@entropitor what does your `.projections.json` file look like and is it located at the root of the mono repo?

I do like this idea and I'm keen to help out implementing projectionist support though I won't have the chance to do so till mid August. Feel free to raise...

@JoosepAlviste are you using projectionist too? I found for me working with mono repos the simplest solution is have each sub project in a tab and in Neovim using `tcd`...

Keen to revisit and solve this issue, it would be quite easy add some unit tests around it because we just need a scenario when you are one directory below....

I've been thinking about this and now feel that handling mono repositories is perhaps beyond the scope of this plug-in and actually warrants its own plug-in for the following reasons:...