feat(browser): inAppIntegration
which uses debugId filenames to determine in_app
on stack frames
#11711
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently in the browser, all stack frames are marked with
in_app: true
which makes it difficult to determine if the error originated from user code or elsewhere.If we have debugIds we can assume that these filenames are the users app code and everything else is not.
This PR adds the
inAppIntegration
that uses the filenames associated with debugIds to determinein_app
. It adds agetFilenameDebugIdMap
function which replaces identical code in 3 other places.