support dependencies across multiple namespaces in wit and cargo component#275
Closed
support dependencies across multiple namespaces in wit and cargo component#275
Conversation
macovedj
force-pushed
the
multi-namespace-deps
branch
from
2ea4ffd to
1610d93
Compare
macovedj
force-pushed
the
multi-namespace-deps
branch
from
1610d93 to
7a9e918
Compare
macovedj
force-pushed
the
multi-namespace-deps
branch
from
9221bb8 to
a072204
Compare
Collaborator
Author
|
Closing in favor of Calvin's PR including warg changes that should simplify quite a bit |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This leverages new changes from
warg-clientenablingcargo-componentandwitto have dependencies across multiple registries/namespaces. The CLIs now take advantage of the namespace mappings that the warg client provides in its local storage.Worth noting... if a user attempts to depend on a package that doesn't exist in the registry they're using, but does exist in another registry that their registry is aware of, it can provide a hint indicating that the user can update their namespace mappings to enable communication with the proper registry. This use case also required the addition of logic to retry many of the CLI commands after updating local namespace storage with the proper hint, preserving the same user experience that the warg CLI has.