Open timaschew opened 8 years ago
+1, this is how I expected it to behave. Using a !
would be a nice way to do it without changing the api
@tyrsius I was for this at first, but that doesn't make a ton of sense now. If you mix blacklist and whitelist, how do you know what to save?
I think an argument to pass as a second parameter makes more sense.
{blacklist: true}
or whatever
Would be nice if the filter would support a path (or array of paths) which is blacklisted instead of white listed.