-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Treat errors from Throw() as plain goja values #1775
Conversation
Hmm I'm not sure this is the way to fix the issue. Even if we don't use goja's |
@na-- I tried porting This approach doesn't produce the same trace as what goja produces internally. Before (as done in #1769):
After (with the ported
Where did you consider adding a type assertion for it? I also think an internal error type would make sense here, but not if it messes up the current logging. |
Sorry for the 6-month late response... 😅 I think we discussed this in Slack, but still should have said something here... 🤦♂️ Anyway, prompted by #2049, I just tried your fix (replacing |
This avoids outputting "GoError" as mentioned in #877 (comment)
f498efd
to
47597c9
Compare
Codecov Report
@@ Coverage Diff @@
## master #1775 +/- ##
==========================================
- Coverage 71.73% 71.70% -0.03%
==========================================
Files 179 179
Lines 14100 14100
==========================================
- Hits 10115 10111 -4
- Misses 3347 3351 +4
Partials 638 638
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. We can either merge this first and I will rebase #2046, or the other way around, 🤷♂️ will be simpler, probably about the same.
This avoids outputting "GoError" as mentioned in #877 (comment) .
I split it off from #1769 to avoid the clutter in that PR.