-
Notifications
You must be signed in to change notification settings - Fork 89
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
Add exclude files to settings.json #617
Comments
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: |
I'm open to that. The other issue with my solution is that it doesn't just hide it from the explorer, it hides it from CTRL + P file navigation as well. |
I'm just not sure where we would put / group all these files / folders under. |
I don't use VS Code, so won't make the change, but my opinion is that we should hide build assets/output and nest infrequently-used files that affect the behaviour of the build and/or tools. Hiding config files would make things more magical and harder to debug. We should exclude these files:
And we should nest these files:
|
Sounds good to me. I think we could also do |
Discussed internally, agreed to avoid nesting altogether, but go ahead with exclusions. Can consider nesting in future. |
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:
The text was updated successfully, but these errors were encountered: