There is no default aliased directory, so I would expect this to fail with the error that no default directory exists when a deployment happens to org3, but instead it is picking the org1 source files and attempting to deploy those. It appears because the aliased packages are using main/default in their folder structure that it is getting matched as "default" in the InstallPackage.ts class (line 147)
I think what we need to do is change our folder structure to the following
Describe the question We have a directory structure in our aliased source packages that is similar to the following.
There is no default aliased directory, so I would expect this to fail with the error that no default directory exists when a deployment happens to org3, but instead it is picking the org1 source files and attempting to deploy those. It appears because the aliased packages are using main/default in their folder structure that it is getting matched as "default" in the
InstallPackage.ts
class (line 147)I think what we need to do is change our folder structure to the following
Just looking for confirmation that the issue is in our folder structure and not a bug.