-
-
Notifications
You must be signed in to change notification settings - Fork 183
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
Improve error message for custom capture #254
Comments
Mmm yeah, that's not ideal and doesn't match the rest of the error reporting. |
It's not a good idea to expose internal details to external users when this library is used for some sort of service. At least the library should provide a way to customize error messages. See also #253 - an attempt to resurrect v1 behaviour on other place. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If custom capture generate an error, then user will receive an error message with full struct name.
panic: Number.Number: problem
An error message with type name or token name will be much better:
<float>: problem
The text was updated successfully, but these errors were encountered: