Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

set value of option noextglob can not work in the below cases #113

Open
APIPLM opened this issue Aug 7, 2022 · 1 comment
Open

set value of option noextglob can not work in the below cases #113

APIPLM opened this issue Aug 7, 2022 · 1 comment

Comments

@APIPLM
Copy link

APIPLM commented Aug 7, 2022

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
@APIPLM
Copy link
Author

APIPLM commented Aug 14, 2022

As I were looking at the implementation of extglob module in file name matching in Ruby, seem like it only implements the pattern "{a,b}" . In Python, it sounds that it does not have it so far, but the function of fnmatch support [seq] and [!seq] as the input of name pattern. I means that why all of implementations in term of this module, they are such different.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant