We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
According to the braces library, braces expansion should not match a single item like {foo}. However, picomatch does interpret this expression.
{foo}
braces:
braces('{foo}') //=> ['{foo}']
picomatch:
picomatch.parse('{foo}').output //=> '(foo)'
Compare that to when there are multiple items:
braces('{foo,bar}') //=> ['(foo|bar)'] picomatch.parse('{foo,bar}').output //=> '(foo|bar)'
It seems to me like the behavior should match in both cases.
The text was updated successfully, but these errors were encountered:
I also find this comment from the README confusing:
Picomatch does not do brace expansion.
Based on my observations, picomatch appears to support all sorts of brace expansion.
Sorry, something went wrong.
Brace expansion is not the same as brace matching.
Expansion does this: {a,b,c} => ['a', 'b', 'c'].
{a,b,c}
['a', 'b', 'c']
braces expansion should not match a single item like {foo}.
Agreed, this is a bug. Thanks for creating the issue.
Aha! That makes sense. Thanks for clarifying.
f9c1a97
No branches or pull requests
According to the braces library, braces expansion should not match a single item like
{foo}
. However, picomatch does interpret this expression.braces:
picomatch:
Compare that to when there are multiple items:
It seems to me like the behavior should match in both cases.
The text was updated successfully, but these errors were encountered: