Consider supporting blacklisting a specific dependency version about antq HOT 6 CLOSED

@lread Thanks for your suggestion!

Not sure what form this exclusion config would take, thought I'd first check if the idea might be of interest.

Indeed.
Sometimes I'd like to ignore specific version.
The feature will help me too :)

We have already --exclude option to ignore specific dependency, so for example, we can extend this option to be able to specify version like --excude=d@v.
(I believe the dep@version format is common because it is used by npm, brew, etc)

from antq.

Yeah, I think that'd work well @liquidz. I currently only see need to blacklist one version, I think(?).

Here's a nuance: Let's say I am at version 1.1.0 of lib x and the current release version is 1.1.2. I know I don't want 1.1.2, so I exclude [email protected]. If there is a v1.1.1 also available, would antq recommend v1.1.1? Or I am I really excluding v1.1.2 and all version before it?

from antq.

@lread

Here's a nuance: Let's say I am at version 1.1.0 of lib x and the current release version is 1.1.2. I know I don't want 1.1.2, so I exclude [email protected]. If there is a v1.1.1 also available, would antq recommend v1.1.1? Or I am I really excluding v1.1.2 and all version before it?

It seems intuitive that [email protected] excludes only v1.1.2.
So v1.1.1 should be reported as available. (because v1.1.0 is outdated)

antq has a version list internally, and it shouldn't be too hard.

from antq.

Sounds good! So if we were wanting to exclude multiple versions of lib x, I would simply specify both [email protected] and [email protected]

from antq.

@lread I've not tested enough yet, but I've tried to add the feature in dev branch.

from antq.

Just released v0.14.0 #76
Feel free to reopen it you have any problems :)

from antq.