Skip to content
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 stacktraces #86

Open
pipermerriam opened this issue Jul 17, 2015 · 0 comments
Open

Improve stacktraces #86

pipermerriam opened this issue Jul 17, 2015 · 0 comments

Comments

@pipermerriam
Copy link
Owner

Currently, when something goes wrong inside of one of the custom validators, it can be really nasty to trace down exactly what is happening. This is largely due to most validation occuring in curried (functools.partial(...)) calls to validation functions which makes tracing down exactly who is passing the wrong type into something frustrating.

Some ideas to fix this are...

  • modify the return value of flex.validation.common.generate_object_validator to have a more descriptive name.
  • modify flex.functional.chain_reduce and flex.functional.apply_functions_to_key to have more descriptive names.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant