-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
TypeError when a filter in catch handler is not a function #1517
Labels
Comments
@marijaselakovic honestly I just use TS which catches that - a PR is welcome I believe though. |
Sure, PR 1518 |
@marijaselakovic sure, can you add a test to the PR that shows the difference in the error thrown? |
Yes, I added the test, which would fail in both versions, but you can see the difference in error messages. Not sure if that's enough |
This was referenced Dec 5, 2019
This was referenced Feb 22, 2020
This was referenced Mar 7, 2020
This was referenced Mar 14, 2020
This was referenced Mar 21, 2020
This was referenced Mar 30, 2020
This was referenced Apr 12, 2020
This was referenced Apr 22, 2020
This was referenced May 7, 2020
This was referenced Jun 8, 2024
This was referenced Sep 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of bluebird is the issue happening on?
3.5.1
What platform and version? (For example Node.js 0.12 or Google Chrome 32)
Node.js v8.5, Ubuntu 16.04.4
Did this issue happen with earlier version of bluebird?
Not sure
If a non-function value is passed as a filter to catch I get the following error: TypeError: Cannot read property 'apply' of undefined
The following code demonstrates this:
You should consider adding a type check on arguments passed to catch.
The text was updated successfully, but these errors were encountered: