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
And our own library function src.barbo is a dependency of lib.foo.b:
src.barbo = lib.foo.b * 4
Furthermore, say we have a patch thepatch that records an update of lib.foo.a to some newer version.
lib.foo.a -> lib.foo.a#newhash
I think the idea behind this ticket is: if I ask todo thepatch, don't tell me that lib.foo.b needs an update, because that's library code that I'm not meant to touch.
But our src.barbo is a transitive dependent of something on the LHS of thepatch (namely lib.foo.a), it's just not on the "edit frontier" of direct dependents.
Do we want to recommend the user starts working through definitions beginning with src.barbo, ignoring all dependents of edited definitions that only have names in lib.*?
I think yes: you can always
cd lib
if you specifically want to see whether your dependencies are curret wrt a patch.The text was updated successfully, but these errors were encountered: