Report uncaught errors in sagas to BugsnagRealized we have a huge hole in our error monitoring—uncaught errorsthat happen inside `redux-saga` call paths are caught by `redux-saga`itself, meaning they’re not captured as uncaught exceptions or unhandledpromise rejections. So, we need to explicitly send them to Bugsnag.Fortunately, `redux-saga` does provide an `onError` callback when creatingthe middleware that actually runs sagas, which is intended for justthis use case. Add that callback and report errors to Bugsnag.
Report uncaught errors in sagas to BugsnagRealized we have a huge hole in our error monitoring—uncaught errorsthat happen inside `redux-saga` call paths are caught by `redux-saga`itself, meaning they’re not captured as uncaught exceptions or unhandledpromise rejections. So, we need to explicitly send them to Bugsnag.Fortunately, `redux-saga` does provide an `onError` callback when creatingthe middleware that actually runs sagas, which is intended for justthis use case. Add that callback and report errors to Bugsnag.

popcodeorg/popcode,outoftime/learnpad,jwang1919/popcode,jwang1919/popcode,jwang1919/popcode,outoftime/learnpad,jwang1919/popcode,popcodeorg/popcode,popcodeorg/popcode,popcodeorg/popcode