allow devs to safely override vscode settings locally (gitignore local.code-workspace) #8478
Description
Increasing access
Currently, the vscode folder settings (.vscode/settings.json) are not gitignored. A developer cannot make local changes to this file to set up the IDE to suit their needs without perpetually risking accidentally either committing or losing their changes.
While they can override settings globally, they may also want to make project-specific changes to suit their needs or preferences. Such changes might include workspace title, key-mappings, zoom level, screen-reader support, workspace theme (font, colours for contrast and readability), autocompletion overrides and dictionary.
Most appropriate sub-area of p5.js?
- Accessibility
- Color
- Core/Environment/Rendering
- Data
- DOM
- Events
- Image
- IO
- Math
- Typography
- Utilities
- WebGL
- Build process
- Unit testing
- Internationalization
- Friendly errors
- Other (specify if possible)
Feature request details
The best override option I've found - assuming .vscode/settings.json continues to be git-tracked - is for the developer to use a .code-workspace file in the project folder for their local preferences. This allows overrides of the project settings.
All this needs from the repo is for the file to be gitignored by the project! I suggest local.code-workspace as a file name to be ignored.