filepaths with dots in them do not match with brace ranges

[starpit]

(Thanks for reporting an issue to micromatch! If you haven't already read the contributor guidelines, Please do that now, then proceed to fill out the details below.)

Please describe the minimum necessary steps to reproduce this issue:

npm init -y
npm install [email protected] 
node
> require('micromatch').isMatch('a.b', 'a.b')
true
> require('micromatch').isMatch('a.000', 'a.000')
true
> require('micromatch').isMatch('a.000', 'a.00{0,1}')
true
> require('micromatch').isMatch('a.000', 'a.00{0..1}')
false /* <---- should be true? */
> require('micromatch').isMatch('a000', 'a00{0..1}')
true

What is happening that shouldn't be?

When a filepath contains a dot, brace range expansion does not seem to work as expected. But brace enumeration expansion seems fine.

What should be happening instead?

It shouldn't matter if the filepath has a dot?

[starpit]

Is this project being maintained? I see a PR that perhaps addresses this... from two years ago?

ref: #170

[jonschlinkert]

It might not be an urgent issue. Read this: https://github.com/jonschlinkert/idiomatic-contributing/#dont

[starpit]

Thanks for the response! I wasn't sure, given the staleness of both.

[jonschlinkert]

I currently have close to 1,000 issues on all of the repos I maintain. I've resolved tens of thousands of issues. We implement automated responses or bots on some big projects, but those systems also need to be maintained.

I will look into this next time I work on this library.

[starpit]

No worries, I completely understand. 👍