-
Notifications
You must be signed in to change notification settings - Fork 9
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
Feature: Better error messages #24
Comments
A small improvement in this area #28 |
This applies to casting fns that are atoms and casting fns that are MFA tuples |
Improved in #40 We could keep evolving the error message that is returned, eg calling the trace we give a schema-trace suggestion it could be something like:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a cast function raises unexpectedly it can be tricky to see what field actually caused it. This can be helped by unit testing the cast fns (so you are sure they handle the cases you expect) and then possibly IO.inspecting the value as it comes in. But it would be nicer to be able to see which field caused the error just straight off the bat.
The obvious thing to do would be to wrap the cast__fns in a try catch but I don't like that at all...
The text was updated successfully, but these errors were encountered: