micromatch / micromatch/picomatch
set value of option noextglob can not work in the below cases
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.3k
- Forks
- 135
- Avg merge
- 23h 38m
- Merged PRs (30d)
- 7
Description
picomatch = require('picomatch')
picomatch.isMatch('a.j.js', '*.*(j).js', { noextglob: true })
=> true
picomatch.isMatch('a.j.js', '*.*(j).js', { noextglob: false})
=> true
picomatch = require('picomatch')
picomatch.isMatch('z', '*(z)', { noextglob: true })
=> true
picomatch.isMatch('z', '*(z)', { noextglob: false})
=> true
picomatch = require('picomatch')
picomatch.isMatch('a.ajj.js', '*.a*(j).js', { noextglob: true})
=>true
picomatch.isMatch('a.ajj.js', '*.a*(j).js', { noextglob: false})
=>true
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests. Start by running the three reproductions and tracing how the noextglob option is handled by picomatch's matcher; done means the option changes extglob interpretation as intended and the reported cases are covered by regression tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100