On the main branch, I have a nested subproject setup whereby metals dont seem to recognise that the subproject within a subproject belongs to the same gradle workspace and prompts to import the project again. This is despite bloop generating the correct json files for all nested subprojects
Describe the bug
Hi guys, ive set up an example gradle project with nested subprojects at this repo here. https://github.com/q-joshualeong/example-scala-metals
On the main branch, I have a nested subproject setup whereby metals dont seem to recognise that the subproject within a subproject belongs to the same gradle workspace and prompts to import the project again. This is despite bloop generating the correct json files for all nested subprojects
Here is what my bloop folder looks like.
When I use metals in VScode, the bloop folder genreated looks similar and metals work there. So i dont think its an issue with bloop or metals.
On the feature/non-nested-structure branch, it just works as expected.
Gradle version: 7.5 Scala version: 2.12.17
Thanks so much!
Expected behavior
nvim-metals should work for nested subprojects in gradle too.
Operating system
macOS
Version of Metals
1.3.5
Commit of nvim-metals
1b87e6bfa417