Skip to content

#140 - Are scope requirements meant to be transitive? #141

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

Closed
wants to merge 2 commits into from

Conversation

rbygrave
Copy link
Contributor

@rbygrave rbygrave commented Aug 3, 2021

If a scope depends on a parent scope and that parent scope has
external dependencies - then the scope should also be able to
depend on those external dependencies.

Ultimately the fix for this is in ScopeInfo.providesDependency()
adding in the check to see if the dependency is in requires
(is an external dependency of the scope).

If a scope depends on a parent scope and that parent scope has
external dependencies - then the scope should also be able to
depend on those external dependencies.

Ultimately the fix for this is in ScopeInfo.providesDependency()
adding in the check to see if the dependency is in requires
(is an external dependency of the scope).
@rbygrave rbygrave added the bug Something isn't working label Aug 3, 2021
@rbygrave rbygrave added this to the 6.6 milestone Aug 3, 2021
@rbygrave rbygrave self-assigned this Aug 3, 2021
@rbygrave rbygrave linked an issue Aug 3, 2021 that may be closed by this pull request
@rbygrave
Copy link
Contributor Author

rbygrave commented Aug 3, 2021

This was merged. Closing.

@rbygrave rbygrave closed this Aug 3, 2021
@rbygrave rbygrave deleted the feature/140 branch December 16, 2021 00:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Are scope requirements meant to be transitive?
1 participant