feat: add JsrVersionResolver trait to allow more control over version resolution
#554
Conversation
This file contains 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
nathanwhit
changed the title
JsrVersionResolver trait to allow more control over version resolution
nathanwhit
commented
Dec 9, 2024
| package_req: &PackageReq, | ||
| ) -> Option<&'a Version>; | ||
|
|
||
| fn force_fetch_metadata<'a>(&self, package_name: &str) -> bool; |
There was a problem hiding this comment.
meh on this, doesn't really feel like it's the right place but adding another trait is annoying
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 is to support specifying versions to use for jsr packages that are not roots (for
deno outdated --update). Currently, as a user of deno_graph there isn't a way to influence the version resolution for non-roots, and there also isn't a way to selectively invalidate cached metadata for packages.