-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
fix(v8/utils): Stack parser skip frames (not lines of stack string) #10560
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
size-limit report 📦
|
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.
Let's add a note to MIGRATION.md
and we can merge this in!
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.
Looks good. My only minor concern is that this modifies the test case to pass and these tests have been around for a long time. But if they were wrong, they were wrong!
@AbhiPrasad I've added the migration information, let me know if it's understandable, or if I should include an example. |
error.framesToPop
#9656In happy scenarios, the
framesToPop
should not make a difference as the Sentry backend will marknonInApp
frames and hide them by default from the user.In other scenarios, when source maps are missing for example, the frames will be visible and shown as the root of an error which is misleading and confusing to our users.
Before this PR
We used
framesToPop
for two unrelated purposes.After this PR
We have two variables each having one purpose.
skipFirstLines
to skip potentially dangerous lines that could be parsed as frames but aren't frames.framesToPop
to remove parsed frames.Notes
This is especially useful for React applications as the framework internally uses the
framesToPop
property. And also for our own SDK.