You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if I have a monorepo, in which there are multiple features declaring the same environment (name + type), their setup calls end environment declarations get mixed up in the same chunk.
Prior to the enviropnment inheritance we failed to notice this, because the setup calls were based on the environment name, but now, they rely on the instance.
Currently, in my monorepo I have 3 features, A, B, C. A declares an iframe environment - export const baseEnv = new Environment('base', 'iframe', 'multi');. B declares an iframe environment, which inherits baseEnv - export const frameEnv = new Environment('frame', 'iframe', 'multi',[baseEnv]);. C declares an iframe environment - export const frameEnv = new Environment('frame', 'iframe', 'multi');
in this case, the bundle of frame env will have both the declaration of the frameEnv as an inherited one and, one not.
This caused the inherited service from baseEnv to not be missing at runtime when used from the frameEnv
The text was updated successfully, but these errors were encountered:
Currently if I have a monorepo, in which there are multiple features declaring the same environment (name + type), their setup calls end environment declarations get mixed up in the same chunk.
Prior to the enviropnment inheritance we failed to notice this, because the setup calls were based on the environment name, but now, they rely on the instance.
Currently, in my monorepo I have 3 features, A, B, C.
A
declares an iframe environment -export const baseEnv = new Environment('base', 'iframe', 'multi');
.B
declares an iframe environment, which inheritsbaseEnv
-export const frameEnv = new Environment('frame', 'iframe', 'multi',[baseEnv]);
.C
declares an iframe environment -export const frameEnv = new Environment('frame', 'iframe', 'multi');
in this case, the bundle of
frame
env will have both the declaration of the frameEnv as an inherited one and, one not.This caused the inherited service from
baseEnv
to not be missing at runtime when used from the frameEnvThe text was updated successfully, but these errors were encountered: