-
Notifications
You must be signed in to change notification settings - Fork 251
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
[PLAT-5010]: Create React Navigation plugin #1067
Conversation
a65f161
to
dd57e42
Compare
packages/plugin-react-navigation/types/bugsnag-plugin-react-navigation.d.ts
Outdated
Show resolved
Hide resolved
packages/plugin-react-navigation/test/react-navigation.test.tsx
Outdated
Show resolved
Hide resolved
Co-authored-by: Joe Haines <hello@joehaines.co.uk>
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.
No comments from a test pespective.
Just curious, what happens with this change if we were already leaving breadcrumbs and setting context? Are we going to end up with duplicate logs? Should be listed as a breaking change if so. |
This plugin has to be installed manually (it doesn't get pulled in automatically by If you'd like to migrate to using the plugin instead of your custom solution, the docs are here |
This PR adds a plugin that integrates with React Navigation.
The new plugin hooks in to
onStateChange
events to perform the following actions:context
so that when an error happens, so the developer can immediately see which screen it happened onNote, end to end tests to follow in separate PRs as it requires a significant amount of @bugsnag/platforms-test-automation input.