chore: Migrate VSCode Workspace/Dev Container Settings #2749
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
re-formatted structure removed deprecated linting settings added pylint extension to replace old linting setting
boc-the-git
approved these changes
Nov 24, 2023
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.
What type of PR is this?
(REQUIRED)
What this PR does / why we need it:
(REQUIRED)
Recent VSCode changes broke most of our linting settings. They provided a nice migration guide:
https://github.com/microsoft/vscode-python/wiki/Migration-to-Python-Tools-Extensions
Thankfully we were mostly using the new extensions, we just had some older configurations too.
Which issue(s) this PR fixes:
(REQUIRED)
N/A
Testing
(fill-in or delete this section)
Pretty sure this fixes everything, I played around to check.