Skip to content
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

Remove or otherwise constrain .vscode settings directory #7

Open
gregoryfoster opened this issue Dec 4, 2022 · 2 comments
Open

Remove or otherwise constrain .vscode settings directory #7

gregoryfoster opened this issue Dec 4, 2022 · 2 comments
Labels
question Further information is requested

Comments

@gregoryfoster
Copy link
Member

Not all users will be using Visual Studio Code, so it's debatable whether we should include a .vscode directory and settings file in our repository as those project defaults may override local settings.

@gregoryfoster gregoryfoster added the question Further information is requested label Dec 4, 2022
@gregoryfoster
Copy link
Member Author

@keeganskeate
Copy link
Contributor

As with everything in life, there are pros and cons to both. I think that for this project we are okay to not include the .vscode directory. Developers using VS Code can refer to other developers using VS Code to get a hold of their preferred settings.json or use their own preferred settings. Developers using other code editors won't need the directory and will have a less cluttered workspace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants