Fix regression causing the global cache directory to be in the wrong location #429
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.
Fixes a regression that causes the global cache directory to no longer be in its correct location as described in the 0.19.2 changelog.
This issue was introduced in 598f319, and also makes the global cache and config folder be the same folder on Linux and MacOS.
Since I was working on this I also took the liberty of changing the cache location on Windows to be inside the proper temp folder so Storage Sense (and third-party programs, should people use those) are able to delete cached files if they'd like to.