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
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.
The text was updated successfully, but these errors were encountered:
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...
flex.validation.common.generate_object_validator
to have a more descriptive name.flex.functional.chain_reduce
andflex.functional.apply_functions_to_key
to have more descriptive names.The text was updated successfully, but these errors were encountered: