Remove outdated docs regarding vscode eslint extension and typescript autofix #8307
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.
I would like to remove documentation that is no longer relevant (outdated). It is regarding ESLint extension for Visual Studio Code and its Typescript support. microsoft/vscode-eslint#609
Before ESLint extension version 2.0.4 (before December 16, 2019 source:
https://github.com/microsoft/vscode-eslint/releases), the extension did not have Typescript support (auto-fix feature) enabled by default and it had to be enabled manually by adding a specific configuration in
.vscode/settings.json
(the block removed by this PR)As aforesaid, this issue with ESLint not having TypeScript support enabled by default has been fixed with version 2.0.4 (released on Dec 16, 2019) and this block of code (workaround) is no longer relevant.
source: https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint
In fact this configuration is now squiggle-lined once added to
.vscode/settings.json
with a warning as shown in the screenshot.