-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
Executables are not found if they are inside folders listed in VS Code files.exclude
option
#113
Comments
I'm using the findFiles endpoint to query files. According to the documentation if the second parameter is null, it should not use the default exclusion pattern. I interpret this that it should work, because I am passing null as second parameter. I might misinterpret the documentation or there is vscode bug. |
Thanks for the quick reply! I guess the easiest way to have both features would be to add |
Nore that “undefined” and “null” are different values in JavaScript. |
I'm bad in JS so I talk only about files detection dependency on I guess this issue could be called a feature request to have independent |
Disagree:
(See doc) |
Oh, I get it now. |
This is current behaviour, but I hope there would be discussion on changing it: |
For default exclude there is They reopened your issue 👍 I will close this if you don't mind and hope that vscode fixes its API. |
I have test executables inside
build/
. I added this folder tofiles.exclude
in order to hide it from explorer tree, but my test executables are also become hidden. Executables are not shown even if I pass relative or absolute path instead of globbing pattern.Is there a possibility to resolve executables pattern even if it intersects with 'files.exclude'?
The text was updated successfully, but these errors were encountered: