Denis Malinochkin
Denis Malinochkin
Sounds like a feature request. JFYI: Right now you can use the following work around: ```js const fg = require('fast-glob'); await fg(['**/*'], { absolute: true, dot: true, ignore: ['{**/*,*}.txt'], //...
Just one question: > Why you use the `{**/*,*}` pattern instead of just a `**/*`? As I know, `**/*` involve `*` and can be interpreted as «entries with `txt` extension...
@reklatsmasters, I think these things are different. Based on the description of this issue – we just want to allow the use `!` in the `ignore` option.
@evilebottnawi, you can provide real case with FS structure (`ls -R` or `tree`) and actual/expected results?
So, look like misunderstanding in the issue description :) I just let you use the negative patterns in the `ignore` option.
Another issue about this functionality — #356. Unfortunately, I could not come up with a decent algorithm that allowed me to implement this functionality without completely rewriting the pattern-matching mechanism...
Another reason: * https://github.com/mrmlnc/fast-glob/blob/19cdcb721c8ee6e07bee3e7a2e86fd43063ecf63/src/tests/smoke/root.smoke.ts#L43
Also: https://github.com/mrmlnc/fast-glob/blob/b9f74dd8aa9d54ad674f9f843d1747dcc12c762d/src/readers/async.ts#L27-L32
Will be covered by `fast-glob@3`.
> `node-glob` does not exclude results from similar patterns. After several approaches: * We don't know which pattern is similar to the other, so we can't drop it from input....