-
-
Notifications
You must be signed in to change notification settings - Fork 142
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
Whitespace in path #66
Comments
If it's failing on a space, that would be a bug. I'm guessing it's not just the space but a combination of the space and something else... I'll take a look, thanks for creating the issue |
Yeah it's the brace pattern. For some reason it appears to be recognizing the whitespace as a boundary or a delimiter. I know where the problem is, I should be able to get a fix pushed up. edit: to clarify, it's not the brace pattern that's causing the issue, it's the |
k, found it, and fixed it. I need to run some tests on braces and micromatch then I can push up |
please reopen if you have any more issues, thanks! |
That was fast. Thanks a lot for the quick fix! |
Any time. I always appreciate getting issues for bugs. We all get busy and it's hard to take a few min and do that sometimes, but this lib is better as a result, so thank you! |
Hi, I'm trying to match files using the following pattern:
micromatch sadly returns an empty array, which is not what I expected. After several experiments I figured out that the whitespace between "ccc" and "2016" might be the reason for it.
Is this a problem of the pattern I'm using or an issue of micromatch? How should I deal with spaces in paths?
Node.js Version: 6.2
micromatch Version: 2.3.8
The text was updated successfully, but these errors were encountered: