-
Notifications
You must be signed in to change notification settings - Fork 142
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
♻️ [RUMF-1508] reorganise error handling #2181
Conversation
Current dependencies on/for this PR:
This comment was auto-generated by Graphite. |
Codecov Report
@@ Coverage Diff @@
## main #2181 +/- ##
==========================================
+ Coverage 93.81% 93.85% +0.04%
==========================================
Files 201 201
Lines 6062 6073 +11
Branches 1337 1344 +7
==========================================
+ Hits 5687 5700 +13
+ Misses 375 373 -2
... and 1 file with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
ffbe29c
to
d8b82b4
Compare
53e2d9d
to
22f22be
Compare
22f22be
to
57f527c
Compare
57f527c
to
d87f16e
Compare
Co-authored-by: Aymeric <[email protected]>
a433851
to
62e2d43
Compare
/to-staging |
🚂 Branch Integration commit 62e2d43 will soon be integrated into staging-17. This build is going to start soon! (estimated merge in less than 0s) you can cancel this operation by commenting your pull request with |
🚂 Branch Integration commit 62e2d43 has been merged into staging-17 |
} | ||
return stackTrace.stack.length > 0 && (stackTrace.stack.length > 1 || stackTrace.stack[0].url !== undefined) |
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.
❓ question: I don't see this check in the original code, why do we need it now?
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.
There are cases where stackTrace.stack = []
or stackTrace.stack = [{url: undefined, column: undefined, line: undefined}]
and we want to use the NO_ERROR_STACK_PRESENT_MESSAGE
for those.
In the original code, those cases happened in the first if but it will change in the following PR.
/to-staging |
🚂 Branch Integration commit 443f8d9 will soon be integrated into staging-17. This build is going to start soon! (estimated merge in less than 34m) you can cancel this operation by commenting your pull request with |
🚂 Branch Integration commit 443f8d9 has been merged into staging-17 |
Motivation
Prepare handling of error without stacktrace
Changes
Testing
I have gone over the contributing documentation.