chore: delete unused vscode settings.json file
#46
Conversation
This file contains hidden or 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
The vscode-eslint version was greater than v3.0.10, which was specified in the the eslint docs (https://eslint.org/docs/latest/use/configure/migration-guide#visual-studio-code-support). So, it was safe to deleted the settings.json file.
StyleShit
changed the title
serttings.json file
StyleShit
changed the title
serttings.json filesettings.json file
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.
Type of change
Deleted the settings.json in the .vscode folder
Details
As asked in the issue, I had to make necessary changes into the .vscode folder.
The vscode-eslint version was greater than v3.0.10, which was specified in the the eslint [docs.]
So, it was safe to delete the settings.json file.
@StyleShit please review this pull request and merge it to solve the issue #43