Migrate VSCode settings.json
#2399
Merged
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
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.
After the last VSCode update, VSCode will now always migrate workspace
settings.jsonfiles automatically. If you discard those changes, it will do it again the next time you open the repo. There is no setting to turn this off. I already did this for spandrel and will go through our other repos too.I fucking hate this. This is about as annoying as the
debug.logfiasco some time ago. Who in their right mind thought that it was a good idea for an IDE to automatically change project files? They should have just kept supporting old settings with an option to migrate settings (e.g. via a button click). Yes, this is more work on their part, but making settings incompatible was also their fault, so they should just take the L.