Skip to content
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

glue and features globbing respects files.exclude but not search.exclude #250

Open
abrenneke opened this issue Sep 26, 2024 · 0 comments
Open

Comments

@abrenneke
Copy link

abrenneke commented Sep 26, 2024

👓 What did you see?

In our monorepo, we have node_modules included in search.exclude but not files.exclude so that node_modules shows up in the file tree in the editor.

However, this causes the rg processes that the extension spawns to take foreeevver because they don't include -g !**/node_modules which means that rg is scanning the entire (gigabytes) node_modules folder.

Adding **/node_modules to files.exclude solves the performance problem we're running into.

✅ What did you expect to see?

I'd expect one of:

  1. Globbing respects search.exclude
  2. Have the ability to add ignore paths to the globbing to speed it up
  3. Automatically ignore **/node_modules?

📦 Which tool/library version are you using?

Cucumber for Visual Studio Code v1.10.0

🔬 How could we reproduce it?

Not really reproducible without a massive node_modules that takes upwards of 10 seconds to scan using rg. But you can note the arguments that are used in the rg process match files.exclude but not search.exclude.

📚 Any additional context?

I tried adding !**/node_modules to cucumber.features and cucumber.glue but unfortunately this gets translated to -g /!**/node_modules which doesn't successfully negate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant