-
Notifications
You must be signed in to change notification settings - Fork 153
feat(logger): improve regex in stack trace parsing #2194
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
feat(logger): improve regex in stack trace parsing #2194
Conversation
c76dba6
to
a7290a3
Compare
a7290a3
to
c58f1cf
Compare
c58f1cf
to
902152e
Compare
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.
Thank you for the PR, I have left just one comment about the regex that I didn't notice when writing the issue but I noticed during review.
Looking forward to merge the PR!
|
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.
Thank you for contributing this improvement, appreciate your time.
I have marked a few more issues in the Logger utility with the help-wanted
label in case you're interested, here's a filtered list.
Description of your changes
This PR improves the regex pattern used to the determine the location of a error in a stack-trace. The newer pattern will support the strackframe locations mentioned in the nodejs documentation.
References:
Related issues, RFCs
Issue number: #2121
Checklist
Breaking change checklist
Is it a breaking change?: NO
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.