Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Mixing directory wildcard and identifier
See original GitHub issueGlob pattern a**/*.cs matches a/b.cs but also matches a/b.md, it should not match a/b.md
The correct pattern should be written as a/**/*.cs, but people make mistakes.
If it is written as a**/*.cs, it should be interpreted as a[Literal] *[Wildcard] *[Wildcard] /[Separator] *[Wildcard] .cs[Literal], and should match ab/c.cs, but is should not match a/b/c.cs or a/b.md
It is also valid to treat consecutive wildcards as an error if it not a directory wildcard.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Alright sounds good. I will go with that then.
yes, I also tried that with node-glob, it should be equivalent to
a*/*.cs. 0.4.0 parsed this pattern just fine.