I’ve used VSCode as my primary text editor for over 5 years now but I’m still learning how best to use it, often through trial and error. Here are a few thin...

Posandu Mapa

Functional Programming

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

Learn how to ignore the .vscode folder in git by using .gitignore_global. Understand why formatters and linter extensions should be enabled at the workspace level. Explore the advantages of using the built-in terminal in VSCode.

Things I wish someone would have told me about configuring VSCode

1. Use .gitignore_global to ignore the .vscode folder

2. Formatters and linter extensions should always be enabled at the workspace level

I love using a global .gitignore, not sure how widely known that feature is. However, I don’t know if having the .vscode folder in there is always a good idea. I’ve worked on some repos where a lot of shared editor settings were added there that helped a lot with onboarding.
Using the workspace settings for linters though is a great tip. I think workspace specific setting are highly unused and can be very powerful.

Great tips, but I could argue about having <code>.vscode</code> in the global <code>.gitignore</code>. I think it’s always a good idea to commit this folder with extensions, tasks and settings used on the project - this way you can align the experience of all developers. This improves not only the experience of an individual, but also the experience of collaboration - you essentially have the same IDE