-
Notifications
You must be signed in to change notification settings - Fork 4
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
Extend ILogger interface to pass Throwables in warning/error calls #168
Comments
The debug option is working great to identify issues. I think the exceptions can be improved upon, to allow for easier debugging especially in production. At the moment we receive stacktraces such as the one attached at the bottom of this comment. It gives a stacktrace for the library but no indication of what the consumer of AndroidBound has done wrong. I would propose the following when propagating errors (wether to a logger or throwing) 1. Throw These would be used when a binding is incorrect. The data would likely be in the form of the message. Data that could be provided..
There could potentially be a number of binding Exceptions.
2. Throw original Exceptions when an exception is received from a method call In other occasions the binding could be correct but when AndroidBound is calling a method via reflection an exception might be received. For example a I don't know the ins and out of this lib too well so I don't know how difficult these things are to achieve.
|
That way their stacktraces can be printed.
The text was updated successfully, but these errors were encountered: