Renderless error management component
Since Sentry is now lazy loaded (4f7a79b8), there is the potential for users to cause errors before Sentry is loaded and initialized meaning those errors wouldn't be reported to Sentry or the user. Implementing a renderless component would provide a central location for error reporting either to Sentry, the user, or both.
Some thoughts to ponder still:
- Should it act as a central hub for errors and allow dev to provide a handler?
- Should it just report to Sentry with an optional dev provided handler?
- Should errors be retained? Should a flushing mechanism be provided if they can be retained?
Edited by Zaba505