We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The line at
ava/lib/serialize-error.js
Line 31 in e9a69dc
if (callsite && callSite.file === normalizedFile) {
since the previous line
const callSite = stackUtils.parseLine(line);
may, and sometimes does, initialize callSite to null. Once this is fixed, if the catch at
callSite
null
Line 39 in e9a69dc
The text was updated successfully, but these errors were encountered:
Thanks, that makes sense. I'll try and get this into the next release if nobody else beats me to it.
Looking at the commit history, the earlier logic checked for a falsy value so I assume the catch isn't needed with this guard.
catch
Sorry, something went wrong.
Hi! Would it be possible for me to work on this?
@Fem-Fem that'd be great!
Thanks! I have a PR here: #2750
b8f5685
Fem-Fem
No branches or pull requests
The line at
ava/lib/serialize-error.js
Line 31 in e9a69dc
should be changed to
since the previous line
may, and sometimes does, initialize
callSite
tonull
. Once this is fixed, if the catch atava/lib/serialize-error.js
Line 39 in e9a69dc
was there only because of this one error, then this do-nothing catch should be removed.
The text was updated successfully, but these errors were encountered: