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
Because strict parenting is enforced when pushing scope, a previously popped global scope cannot be resolved otherwise it may result into errors if it is pushed from a different path.
E.g.
push flavor global=true
push app-type global=true
push media global=false
pop media
pop app-type
push media global=false
The last push fails because flavor.app-type.media is resolved instead of creating flavor.media and flavor.app-type.media is not a direct child of flavor.
Fix
We need to update Context.popScope to clear the edge and merge the values in the parent scope.
Compatibility
If this issue impacts older releases of the engine, we will need to start processing the archetypes at build time to produce compatibles scripts.
The text was updated successfully, but these errors were encountered:
Fixeshelidon-io#1069
- Update Context.popScope to clear the edge and merge values in the parent
- Move ContextScope.isModel to ContextValue.isModel as values are propagated
- Add support for handlebar tag escape with []
- Cleanup OutputGeneratorTest.testContextValues
- Fix MergedModelTest.testResolveWithNonRootContext to use a global context
Problem
Popped global scopes are incorrectly resolved.
Because strict parenting is enforced when pushing scope, a previously popped global scope cannot be resolved otherwise it may result into errors if it is pushed from a different path.
E.g.
The last push fails because
flavor.app-type.media
is resolved instead of creatingflavor.media
andflavor.app-type.media
is not a direct child offlavor
.Fix
We need to update
Context.popScope
to clear the edge and merge the values in the parent scope.Compatibility
If this issue impacts older releases of the engine, we will need to start processing the archetypes at build time to produce compatibles scripts.
The text was updated successfully, but these errors were encountered: