Non-filepaths matchs

[arcanis]

Please describe the minimum necessary steps to reproduce this issue:

Ref: yarnpkg/berry#3460

In Yarn, we have a feature that lets our users silence some error messages if they match specific glob pattern. The problem we have is that those messages sometimes feature slashes (for instance, Package name @scope/name isn't allowed). Glob patterns currently don't interact well with those, since Package name * isn't allowed won't match the /. Using ** helps a bit, but not in every case and it feels like a hack.

What should be happening instead?

We'd want an option that would let us instruct micromatch that * are supposed to transpile into .* rather than [^/]* (even better would be to make it configurable, for example if we want * to be [^ ]* and ** to be .*).

[jonschlinkert]

@dawgwe1 you've been blocked

[jonschlinkert]

hi @arcanis, sorry for the late reply

We'd want an option that would let us instruct micromatch that * are supposed to transpile into .* rather than [^/]* (even better would be to make it configurable, for example if we want * to be [^ ]* and ** to be .*).

That seems doable, and shouldn't be too difficult. Just to ensure I understand clearly what you want, you basically just want an option to customize behavior of * and **, so that you can more intelligently match around other non-standard path characters, correct?

I'll be catching up on some issues this week, I'll see if I can implement something for this.

[arcanis]

Yep, exactly 👍