-
Notifications
You must be signed in to change notification settings - Fork 3.4k
mix deps.update
should propagate dependencies
#1036
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
Comments
This should probably be implemented after caching of dependencies is added. If we could store all dependencies as a tree this issue would be trivial to implement. |
You are right. What I had in mind was simply to store the deps of each project inside If we really want the tree, we could implement it and have it spit out an iterator whenever we want to iterate it. :) |
Ok, the tree can just as well be inline in the current data structure - no need to make an explicit tree. |
That's kind of what we have right now but it would still require you to go through multiple loops in order to get all affected dependencies because the flat structure has no idea of nesting (we just know they are properly ordered). |
If I update dependency
:a
and:b
depends on:a
,:b
should be recompiled by default (otherwise someone doing a full checkout can get a different result).The text was updated successfully, but these errors were encountered: