You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
windows path separators - (how) should matching behavior differ on windows vs. other platforms?
leading ! - behavior of a single or multiple consecutive !
** preceded by or followed by parens, brackets, or braces. In bash, ** only match slashes when it is the only thing in a path segment. However, since non-bash globbing isn't constrained to the same rules as bash (since bash globbing rules are designed to avoid collision with other bash syntaxes), we can support more regex features. For example, the following pattern (in node.js) would conditionally match the preceding ./ in a filepath: ?(./)**/*.js. IMHO, that should be a valid pattern.
braces as regex quantifiers
behavior of +, ? and * following brackets, parens, or braces
The text was updated successfully, but these errors were encountered:
List of edge cases that need to be addressed:
./
!
- behavior of a single or multiple consecutive!
**
preceded by or followed by parens, brackets, or braces. In bash,**
only match slashes when it is the only thing in a path segment. However, since non-bash globbing isn't constrained to the same rules as bash (since bash globbing rules are designed to avoid collision with other bash syntaxes), we can support more regex features. For example, the following pattern (in node.js) would conditionally match the preceding./
in a filepath:?(./)**/*.js
. IMHO, that should be a valid pattern.+
,?
and*
following brackets, parens, or bracesThe text was updated successfully, but these errors were encountered: