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

Allow arbitrary negation locations? #35

Open
tommy-mitchell opened this issue Aug 10, 2023 · 2 comments
Open

Allow arbitrary negation locations? #35

tommy-mitchell opened this issue Aug 10, 2023 · 2 comments

Comments

@tommy-mitchell
Copy link

concurrently supports wildcards and negations like this:

concurrently "npm:lint:*(!fix)"

I'm trying to implement the same syntax in one of my own CLIs. Is this something matcher could support?

@sindresorhus
Copy link
Owner

I'm not sure I want to complicate this package with this, but I'm not saying "no" either.

@sindresorhus
Copy link
Owner

sindresorhus commented Aug 16, 2023

Some things that needs to be clarified:

  • Does the negation have to come right after the wildcard?
  • Should it support multiple negations? How would that look like?
  • How should escaping work? If you need literal parens.
  • This would be a breaking change. How should it be handled? Opt-in?

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

2 participants