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

edge cases #3

Open
jonschlinkert opened this issue Sep 1, 2018 · 0 comments
Open

edge cases #3

jonschlinkert opened this issue Sep 1, 2018 · 0 comments

Comments

@jonschlinkert
Copy link
Member

List of edge cases that need to be addressed:

  • leading ./
  • 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
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