Skip to content

Add VS Code Extensions & Settings Configs #41498

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 29, 2025

Conversation

coliff
Copy link
Contributor

@coliff coliff commented May 27, 2025

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 website
  • dbaeumer.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 templates
  • streetsidesoftware.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

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Refactoring (non-breaking change)
  • Breaking change (fix or feature that would change existing functionality)

Checklist

  • I have read the contributing guidelines
  • My code follows the code style of the project (using npm run lint)
  • My change introduces changes to the documentation
  • I have updated the documentation accordingly
  • I have added tests to cover my changes
  • All new and existing tests passed

Live previews

N/A

@mdo
Copy link
Member

mdo commented May 29, 2025

Lovely, thank you kindly!

CleanShot 2025-05-29 at 12 06 03@2x

@mdo mdo added this to v5.3.7 May 29, 2025
@github-project-automation github-project-automation bot moved this to To do in v5.3.7 May 29, 2025
@mdo mdo merged commit fd879c0 into twbs:main May 29, 2025
14 checks passed
@github-project-automation github-project-automation bot moved this from To do to Done in v5.3.7 May 29, 2025
@coliff coliff deleted the dev/coliff/add-vscode-extensions-settings branch May 30, 2025 00:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Add .vscode/settings.json & extensions.json files to project
3 participants