Proposal: vscode project settings using 2 files #41215
Labels
config
VS Code configuration, set up issues
*duplicate
Issue identified as a duplicate of another issue(s)
Seems like some people prefer to commit the .vscode file to git and some other don't.
YouTube video discussion
In large projects this configuration can be annoying.
I propose to have one file to be committed (the team default configurations) and another one that overwrite the previous one that never must be committed.
Just like on npm with the dev packages installations
What do you think? 🤔
What names do you propose?
The text was updated successfully, but these errors were encountered: