File Order "more precise pattern" seems buggy

[MichaelBailly]

Hello there,

I'm using your wonderful library and encountered a problem. We follow some style guide, and so we got test files in the same folders than library files. In order to match "everything that is not a test file", we use the pattern '**/!(*spec).js'. We also have one file that we absolutely need to have before the others.

So, taking back the layout of the README.md file, if you do a

var files = glob.sync([
  'files/b.txt',
  'files/**/!(*spec).txt'
]);

The library will answer:

[ 'files/a.txt',
  'files/b.txt',
  'files/c.txt',
  'files/x/y.txt'
  'files/x/z.txt' ]

Obviously b.txt is not on top. WDYT ?

Thanks, regards

[jpillora]

Thanks! Yes, that's right! It needs some smarts to better compare the precision of:
files/b.txt and files/**/!(*spec).txt. Currently, the latter – even with the *s removed – is longer than the former so it's treated as more precise. We could add logic, any pattern with ** in it is always "less precise" than others? Are you able to send a PR?