feat: add errorFilter option to bypass incrementing failure stats

[lance]

Refs: #262

Still requires documentation.

[lance]

@RidgeA @ComputerWolf @jahredhope please take a look at the requested feature as implemented and let me know what you think.

[jahredhope]

Awesome, this looks like it's solve my problem perfectly. Thanks.

[RidgeA]

@lance
This is exactly what I expecting. Looking forward to a landing of this PR.

I have only one doubt - wouldn't be better to accept as an errorHandler promise/async function as well?
Personally I don't nee this at the moment, but it could be useful in some cases?...

[ComputerWolf]

@lance, yes, thank you for taking the time to implement this!

[lance]

@RidgeA I'm concerned about asynchronous execution here - not sure why exactly, but in my thinking, the errorFilter function should be simple and straightforward, only checking the result of a received error. I can imagine a scenario where you might want to call a remote service to determine if the error should really be considered an error. But at first blush, that sounds overly complex and might indicate that the architecture should be reconsidered.

[RidgeA]

@lance
Totally agree, this is could be redundant.
Anyway, if someone will need this feature - they could open a new issue and make PR to enhance the errorHandler

[lance]

@RidgeA @ComputerWolf @jahredhope this has been merged. It will be a few weeks before it lands in a release, but you should be able to use it in a package.json now directly from GitHub.

[RidgeA]

@lance
Thanks a lot!

[RidgeA]

Hi @lance,
could you give hint when these changes will be in npm?
My company rules prohibit the use of public packages from git repos directly, only NPM...

Thanks!

[lance]

@RidgeA I understand - I will try and push a new version today or tomorrow.

[RidgeA]

@lance, would appreciate, thank you!

[lance]

@RidgeA I just published v1.11.0 which includes this change.