-
-
Notifications
You must be signed in to change notification settings - Fork 633
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
Pass-through JS error to client #521
Conversation
@justin808 @robwise Please look - this is the most minimalist intrusion into error I can imagine. We just update the message and rethrow same error with all same parameters, incl. stacktrace |
Looking good. @robwise Take a look. @samnang @robwise I don't see any worthwhile way to test this. I think we can skip a new test for this change. Reviewed 1 of 1 files at r1, 2 of 2 files at r2. node_package/src/handleError.js, line 38 [r1] (raw file):
const handleError = (option) => { export default handleError; Comments from Reviewable |
I think this is a good compromise. Also, if we are going to be modifying original error messages like this, we should tell the user who is doing it. So Or something |
@dzirtusss Let's apply Rob's suggestion and call it good! |
Done. What about |
(Yes keep) Reviewed 2 of 2 files at r3. Comments from Reviewable |
I'll merge once CI passes! |
@dzirtusss Can you please update the CHANGELOG.md. |
👏 |
Pass-through simple version of #485
This change is