You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The name of our TryCatch integration is confusing as it doesn't convey what the integration actually does but it rather suggests how it does things.
For reference, the TryCatch integration instruments callbacks of timer functions (setTimeout, setInterval, etc.) to better handle errors within the timers' callbacks. It does so by wrapping them in try/catch blocks but this is an implementation detail rather than the purpose of the integration.
Solution Brainstorm
Proposed new name:
TimerFunctions
WrapTimerCallbacks
Definitely open to other ideas ;)
Note: We can backwards compatibly introduce the new named integration before directly working on v8 and deprecate the old name but we should discuss if this is worth the bundle size hit, given that it's a default integration anyway and not a lot of users will use it directly.
The text was updated successfully, but these errors were encountered:
…egration` (#10755)
Resolves#8838
- Removes `TryCatch` integration class export
- Updates angular to refer to browserApiErrorsIntegration by name
instead of using `TryCatch`
…egration` (#10755)
Resolves#8838
- Removes `TryCatch` integration class export
- Updates angular to refer to browserApiErrorsIntegration by name
instead of using `TryCatch`
Problem Statement
The name of our
TryCatch
integration is confusing as it doesn't convey what the integration actually does but it rather suggests how it does things.For reference, the
TryCatch
integration instruments callbacks of timer functions (setTimeout
,setInterval
, etc.) to better handle errors within the timers' callbacks. It does so by wrapping them in try/catch blocks but this is an implementation detail rather than the purpose of the integration.Solution Brainstorm
Proposed new name:
Definitely open to other ideas ;)
Note: We can backwards compatibly introduce the new named integration before directly working on v8 and deprecate the old name but we should discuss if this is worth the bundle size hit, given that it's a default integration anyway and not a lot of users will use it directly.
The text was updated successfully, but these errors were encountered: