hikinggrass
commented
2 years ago Is the idea here, to check for existing sibling directories, and if they match any of the requirements, use them as these? What about additional directories that aren't any dependencies?
exactly, this removes the reliance on workspace.yaml files that have shown to be a major source of confusion and friction in the past. For example if you copy a whole workspace you most certainly have workspace.yaml in the new directory pointing to dependencies in the old directory.
Additional non-dependency directories should just be ignored
workspace.yaml files are not needed anymore, from now on it is assumed that the parent directory is the workspace
speedup of tag and rev detection for cached dependencies