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

Wildcard filters #219

Milestone

Comments

@jonathanong
Copy link

writing something like ncu -a '/^babel-.*$/' is weird to me. i should be able to just write ncu -a babel-*

@raineorshine
Copy link
Owner

I agree that wildcard expressions would be a nice addition.
On Tue, Mar 1, 2016 at 12:00 PM jongleberry [email protected]
wrote:

writing something like ncu -a '/^babel-.$/' is weird to me. i should be
able to just write ncu -a babel-


Reply to this email directly or view it on GitHub
#219.

@raineorshine
Copy link
Owner

I added support in the "wildcards" branch, but's going to have to wait till the next major version release since it is technically a breaking change. If others are interested in seeing this feature sooner rather than later, please post here.

@raineorshine raineorshine added this to the 3.0.0 milestone Mar 20, 2016
@raineorshine
Copy link
Owner

Closing for cleanup purposes and adding the revive-me label. Feel free to re-open if you are interested in working on a pull request.

@AdrianoCahete
Copy link

This simplified version was merged to the main code?

@raineorshine
Copy link
Owner

raineorshine commented Mar 7, 2021

No, I shouldn't have closed it. In fact, since * is not a valid character in a package name, it shouldn't require a breaking change. Unfortunately the wildcard branch got permanently deleted so it needs to be recreated.

@raineorshine raineorshine reopened this Mar 7, 2021
@raineorshine raineorshine changed the title simplified regex patterns Wildcard filters Mar 7, 2021
@raineorshine
Copy link
Owner

Fixed and published to v11.2.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment