-
-
Notifications
You must be signed in to change notification settings - Fork 200
Origin Location Parsing Improvement #872
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
Conversation
…e how origin location is displayed
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #872 +/- ##
==========================================
+ Coverage 86.19% 91.49% +5.30%
==========================================
Files 17 58 +41
Lines 1318 6316 +4998
Branches 199 199
==========================================
+ Hits 1136 5779 +4643
- Misses 162 517 +355
Partials 20 20
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
@jamessimone this looks great, it's ready to merge! Let me know if you want me to handle merging + release notes, or if you'd like to do it.
I'll do it! |
Slight tweak to origin location stack trace parsing in Apex to improve how origin location is displayed
Noticed while we were cross-checking the following issue: jamessimone/apex-rollup#683 (comment)