Closed fwinkelbauer closed 7 years ago
Sorry yes this is a bug as it shouldnt match.
Bumpy*/**/AssemblyInfo.cs
should be required to match that second case.
I'll add a test case and investigate, thanks for raising.
I have found a quirk. If you set some global options (should not be necessary though) then this behaves as expected:
GlobParseOptions.Default.AllowInvalidPathCharacters = true;
This option to allow you to use invalid path characters in a glob pattern is something I added very recently so I expect it has introduced this bug! If you need a temporary work around, you can resort to the above, either way I'll get a fix out sometime soon.
Take your time! Thank you!
Fixed as of version 1.6.5 - thank you for reporting this.
Hi,
I just found an unexpected match when fiddling around with your library. I am not sure if this is a bug, or if my understanding is lacking: