Cache control for project.json restore #120
Closed
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
|
Can we add tests for this change? |
|
|
| { | ||
| get | ||
| { | ||
| return GetCacheTime(ListMaxAge, DefaultCacheAgeLimitNupkg); |
There was a problem hiding this comment.
This should be NupkgMaxAge
|
|
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 change adds a CacheContext to RestoreRequest to provide more options beyond NoCache. For package installs and updates restore will go by the time the package operation was started, all older cache entries for the packages restored will be cleared out of the v3-cache. After the operation rebuilding and restoring from the command line will work using the updated v3-cache content, instead of having to retrieving it again which would be the case with NoCache=true.
NuGet/Home#1096
//cc @yishaigalatzer @davidfowl @MeniZalzman @deepakaravindr @feiling