-
Notifications
You must be signed in to change notification settings - Fork 215
Update default file exclusions #1336
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
Conversation
a7e232e
to
197e1c7
Compare
These need to be unambiguously ignorable so paths like `target`, `build`, `cache`, etc… should not go here
d9b63e5
to
0933d82
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
To we want to somehow take the @source
information into account in case you do want to enable intellisense in one of these folders?
I'm thinking of the Laravel folks that use vendor
(we are not excluding vendor
in this case so not an issue for them. Just thinking out loud here)
For now, I'm thinking not. This list shouldn't ever contain things like This not only affects whether or not files can show hovers/completions/diagnostics but also the discovery of CSS files in the first place. |
IntelliSense, by default, ignores files for:
.git
,.hg
,.svn
)node_modules
)I'm adding three more groups to this:
.venv
,venv
).yarn
).next
,.turbo
,.parcel-cache
,__pycache__
)Discovered that we should update these when triaging #1312 (that one was specifically about python virtual envs)