Add VS Code Extensions & Settings Configs #41498
Merged
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
Fixes: #41496
Add VS Code Extensions & Settings Configs
Motivation & Context
Adding these configs will mean that the code quality of contributed PRs may improve as bugs, spelling mistakes and linting issues are fixed earlier (in the users IDE, before even making a pull request).
The recommended extensions:
EditorConfig.EditorConfig
- this one's good for removing trailing spaces, ensuring indents are 2 spaces and ensuring files have a final newline.astro-build.astro-vscode
- useful syntax highlighting, intellisense completion, formatting, inlay hints and more for anyone working on the websitedbaeumer.vscode-eslint
- real-time linting of ESLint with autofix option.hossaini.bootstrap-intellisense
- the best Bootstrap intellisense extension - useful for working on examples and website templatesstreetsidesoftware.code-spell-checker
- this extension automatically uses the cSpell config in the project root and can highlight typos in the IDE.stylelint.vscode-stylelint
- this can automatically fix and format all the scss files to match the Stylelint config.The
.vscode.settings
file in this PR is quite light as it stands, but I think can be improved/expanded upon to use specific formatters for more file-types... but as it stands I think these are already valuable additions to the project and can improve the developer experience :-)Type of changes
Checklist
npm run lint
)Live previews
N/A