Open mjclarke94 opened 2 weeks ago
Ran into this need aswell. Was trying to move away from hatch relative packages. But the resolver did not like just pointing to a workspace package in a git repo with sub directory packages as workspace members.
You really just want to specify the git path and revision once for the full workspace set.
We are trying to centralise all of our libraries in a mono-repo, some of which are interdependent.
Rather than needing to add each subdirectory as a source, it would be nice to be able to add all the modules belonging to a virtual workspace as one source which exposes multiple packages.
EDIT: Realised that 0.42.9 fixed my original issue so turning it from a two parter into a more targeted request!