[PLAT-5000] React Native promise rejection stack trace processing #812
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.
Goal
This change allows BugsnagReactNative to convert the native promise rejection stack trace provided by React Native into an array of BugsnagStackframe objects, so that it can be captured as a BugsnagError.
Design
See ROAD-801 for details of the design and specification.
Changeset
[BugsnagStackframe stackframesWithCallStackSymbols:]
was added, which will be invoked by BugsnagReactNative.Testing
Unit test cases have been added to verify the processing of passed in call stacks into BugsnagStackframe objects.
End-to-end automated tests will be covered in bugsnag-js