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
We have a dependents section on the crate page but it currently has placeholder text, so we need to implement reverse dependencies there. More importantly however, we need to make sure the user has the VISIBLE permission for each of these crates when pulling them
The text was updated successfully, but these errors were encountered:
Don't think there's any cheap/elegant way of doing this at the moment, the way cargo informs us that a crate is from the same registry is passing registry as null for each dependency. But obviously it isn't aware of orgs, so we:
have to guess whether or not the depedency is from chartered based on ssh://127.0.0.1:2233/core (check if begins with ssh://?), and
we have to do a db lookup for each organisation passed to lookup by name and get the id for the db relationship.
bit of a pain really, think we should just hide the 'dependents' section for now.
w4
added a commit
that referenced
this issue
Sep 28, 2021
We have a dependents section on the crate page but it currently has placeholder text, so we need to implement reverse dependencies there. More importantly however, we need to make sure the user has the VISIBLE permission for each of these crates when pulling them
The text was updated successfully, but these errors were encountered: