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
Is your feature request related to a problem? Please describe.
Just getting Error Details (exception, reason, stack) limits the ability to provide more context information. You can run into situations where just having these isn't enough to identify the cause and you want to send additional information like local variables or the arguments that were passed in to the crashing function. In my case I want to attach custom properties to a Crashlytics report.
Describe the solution you'd like
You should be able to set an optional dynamic object to the handle method, that then can be accessed in a talker observer.
Example of calling .handle:
final item =getItemById(id);
try {
// Something might throw when using the amount
}
catch(e,st){
final context = {"itemAmount": item.amount};
talker.handle(e,st, "Couldn't modify item amount", context);
}
Is your feature request related to a problem? Please describe.
Just getting Error Details (exception, reason, stack) limits the ability to provide more context information. You can run into situations where just having these isn't enough to identify the cause and you want to send additional information like local variables or the arguments that were passed in to the crashing function. In my case I want to attach custom properties to a Crashlytics report.
Describe the solution you'd like
You should be able to set an optional dynamic object to the handle method, that then can be accessed in a talker observer.
Example of calling .handle:
Example of a TalkerObserver using the context
Describe alternatives you've considered
Alternatively you could write your own error handler, but you would lose all the benefits of this package.
Additional context
The idea with additional context information is based on structured logging in the .net world.
The text was updated successfully, but these errors were encountered: