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
{{ message }}
This repository has been archived by the owner on Feb 3, 2018. It is now read-only.
Because the ExternalReach() function is focused entirely on external imports, it entirely omits any internal packages that may be a part of that import chain. As a result, we end up missing packages in deps that are only imported internally.
For example, if our root project imports a, and (only) a imports a/foo, then a/foo will not show up in the packages list.
The fix for this is fairly complicated. I'll have to roll it in as part of #148.
The text was updated successfully, but these errors were encountered:
Once I saw it, this was a big, obvious 🤦♂️ .
Because the
ExternalReach()
function is focused entirely on external imports, it entirely omits any internal packages that may be a part of that import chain. As a result, we end up missing packages in deps that are only imported internally.For example, if our root project imports
a
, and (only)a
importsa/foo
, thena/foo
will not show up in the packages list.The fix for this is fairly complicated. I'll have to roll it in as part of #148.
The text was updated successfully, but these errors were encountered: