Watchman does not understand micromatch globs about sane

[conartist6]

I think the thing to do is to parse the glob, then potentially warn and fall back. I'll work on a PR.

[conartist6]

Hmm, it's more interesting than that I guess. Here's what watchman actually supports for globbing: https://github.com/facebook/watchman/blob/061e6abd75449256e00cd8880b94d030f3360ee4/tests/wildmatch_test.json

[conartist6]

I opened a PR for option 2 since it's the simplest correct behavior.

[conartist6]

Also it seems like wildglob supports [!...] and [^...] for negated character classes where ... is characters which should not be part of the class. It seems that micromatch only supports [^...].

[conartist6]

Fortunately it should be possible to use the parser to translate from [!...] to [^...]

[conartist6]

er, actually I guess the translation would be from [!...] to [\!...]

[conartist6]

I'm also going to follow up with watchman and see if it would be possible for them to gain more support by using fnmatch

[conartist6]

Oh, and it looks like sane can gain at least braces support for watchman using micromatch.braces(glob, { expand: true })

[conartist6]

Unfortunately I none of the glob parsers I've found (save glob-parse, which is hardly well supported) give me the flexibility to identify the source text of POSIX brackets glob segments, so for the moment I think it's OK to let that smaller issue persist.