Open isaacabraham opened 2 weeks ago
I agree on excluding the first part of the list, second part not so much. I feel like those files tend to be a source of issues that can be fairly hard to pinpoint because they are in config files. For people not as familiar with the template hiding part of the config can make troubleshooting more challenging that necessary.
@isaacabraham what are your thoughts on Maxime's preferred solution to this problem - nesting config under a single file using this extension: https://github.com/antfu/vscode-file-nesting-config
We should consider excluding folders from VS Code. This can be included in the
settings.json
file:This is just an idea - the list above might be too much though. Certainly the first half of the list would be good to add - the second half might be more controversial ;-)
Before:
After: