Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MergedModel.resolveModel should not require the root scope #878

Closed
romain-grecourt opened this issue Feb 1, 2023 · 0 comments · Fixed by #923
Closed

MergedModel.resolveModel should not require the root scope #878

romain-grecourt opened this issue Feb 1, 2023 · 0 comments · Fixed by #923
Assignees
Labels
3.x archetype bug Something isn't working
Milestone

Comments

@romain-grecourt
Copy link
Contributor

The root scope can only be required when doing a full traversal. However MergedModel.resolveModel can be used to resolve scope model and in that case the scope cannot be expected to be the root scope.

We should remove the method Context.requireRootScope() and instead update Controller.walk to enforce that the context scope is same before and after traversal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.x archetype bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants