Often when writing Python code, you will need to validate one or more conditions about a value, and raise an error if those conditions aren't valid. The most simple example is as follows:
def inverse(value):
# Validate that the input is a positive number
if not isinstance(value, (int, float)):
raise ValueError("Value must be either an int or a float")
if not value > 0:
raise ValueError("Value must be positive (non-zero)")
return 1 / valueThis works for very simple cases, but what if we wanted to format more information into the error messages? What if we want a custom error type to represent specifically a validation error? What if we need to do 20, or 200 validations, instead of 2? You can start to see how quickly your boilerplate for validation could clutter up your code.
onecondition aims to solve this issue with a simple design philosophy:
You should only have to write one line of code in order to validate one condition.
(And that line should be less than 100 characters long.)
The most common usage of onecondition is to validate that the parameters passed to a function are valid.
The validate submodule provides a large number of functions that allow validating many aspects about a value.
import onecondition as oc
import onecondition.validate
def inverse(value):
# Validate that the input is a positive number
oc.validate.instance(value, (int, float))
oc.validate.positive(value)
return 1 / valueNow, if you run something like inverse(4), you will get the expected output of 0.25.
However, running inverse(0) would give the following error:
Traceback (most recent call last):
...
onecondition.ValidationError: Value `0` must be positive (non-zero)
Similarly, running inverse("foobar") would result in the following:
Traceback (most recent call last):
...
onecondition.ValidationError: Value `'foobar'` must be an instance of (<class 'int'>, <class 'float'>), not a <class 'str'>
Isn't that much nicer than writing all that code yourself?
