Basename breaks matching complex pattern

[TrySound]

(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:

Hi, I tried to use micromatch for prettier I got a failed test with this case

mm.isMatch("__best-tests__/file.js",["**/__best-tests__/*.js"], {basename: true})
// with basenname: true the result is false
// with basename: false the result is true

I wasn't able to make it work with absolute path as well

mm.isMatch("/user/__best-tests__/file.js",["**/__best-tests__/*.js"], {basename: true})

What is happening that shouldn't be?

Correct pattern doesn't work with basename: true

What should be happening instead?

It should match. But I'm not sure. Works with minimatch.

[TrySound]

From docs looks like basename matcher should not be used if pattern contains slashes.

If set, then patterns without slashes will be matched against the basename of the path if it contains slashes.

And this actually matches minimatch bahavior. With filtered patterns I was able to pass prettier tests.

  const withSlashes = [];
  const withoutSlashes = [];
  for (const pattern of patternList) {
    if (pattern.includes("/")) {
      withSlashes.push(pattern);
    } else {
      withoutSlashes.push(pattern);
    }
  }
  const result = micromatch.isMatch(filePath, withoutSlashes, {
      ignore: excludedPatternList,
      matchBase: true,
      dot: true,
    }) ||
    micromatch.isMatch(filePath, withSlashes, {
      ignore: excludedPatternList,
      matchBase: false,
      dot: true,
    })

[HackAttack]

Root issue seems to be micromatch/picomatch#89.