When one target of a repo would specify a version, but another target for the same repo, but another sub-dir, wouldn't, this will cause a misalignment of the submodules. As sub-dir A will be checkout to version1, with the submodule(s) in that sub-dir to match with version1. But when sub-dir B is checked out to version2, sub-dir A will also be checked-out to version2. The submodule(s) of sub-dir B will be checked out to match version2, but the submodule(s) in sub-dir A, will still be matching version1.
The question is whether we should cover such a situation, as one target is overruling the version of another target.
When one target of a repo would specify a version, but another target for the same repo, but another sub-dir, wouldn't, this will cause a misalignment of the submodules. As sub-dir A will be checkout to version1, with the submodule(s) in that sub-dir to match with version1. But when sub-dir B is checked out to version2, sub-dir A will also be checked-out to version2. The submodule(s) of sub-dir B will be checked out to match version2, but the submodule(s) in sub-dir A, will still be matching version1.
The question is whether we should cover such a situation, as one target is overruling the version of another target.