chore: recommend specific vscode extensions to setup development [skip ci] #377
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
cino
changed the title
SpecialAro
force-pushed
the
vscode-extensions-recommendation
branch
from
15a116d
to
0266474
Compare
SpecialAro
approved these changes
Jun 27, 2022
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.
Description of Change
Based on the project setup and contributing.md I'd like to suggest a couple of basic vscode plugins to the ./vscode/extensions.json to let vscode inform people of which plugins to use.
Motivation and Context
So that everyone that uses vscode will be advised to install these plugins, and get all the benefit of the prettier/eslint/gitignore/editorconfig files in the editor.