What is the difference between matcher and filter? about micromatch HOT 7 CLOSED

I can't speak to why both needed to be provided in the API, but here's the difference as far as I can tell:

filter works with one or more glob patterns.

matcher works with one criterion (not an array) and allows regexes and functions as well as glob patterns as the input.

from micromatch.

Yeah, the differences that @es128 pointed out are correct, but I've thought about removing filter. Maybe we can allow matcher to handle multiple patterns, and get rid of filter next time we make major changes

from micromatch.

Maybe we can allow matcher to handle multiple patterns, and get rid of filter next time we make major changes

That sounds good, less confusing.

In the mean time, do I understand correctly that mm.filter(x)(filename) should always work identically to mm(filenames, x), no matter what type x is?

from micromatch.

What's the use case? might be easier to give good feedback based on what you're trying to accomplish.

from micromatch.

The mm() function works like this:

Negation patterns:
Behavior;

• when the pattern is a string, minimatch behavior is used, so patterns are inclusive by default.
• when an array of patterns is passed, multimatch behavior is used, so patterns are exclusive by default

Does the function I get back from mm.filter(x) have that same behaviour (i.e. it can either be inclusive or exclusive, depending on whether x is an array or a string)?

from micromatch.

can [filter] either be inclusive or exclusive, depending on whether x is an array or a string)?

it should, yes. see these unit tests for examples

from micromatch.

closing since it's not technically an issue. feel free to continue the conversation or open a new issue if a new topic pops up

from micromatch.