| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Struct-level validation has been changed in b31fd25cc5cec96ccee737ba1313c6e9f702f32a, but it appears the README was not completely updated: the return value for struct-level validation refers to the old functionality.
|
|
added installation instructions
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Issue #69: Change `range` to require only one arg
|
|
Close #65
|
|
Currently range is hard-coded to take both max and min. This is
unhelpful in cases where we may only want to check one of the bounds.
Update so that it behaves more like the `length` validator and can take
either max or min, as well as both. Also ensure that at least one of
them is supplied.
|
|
|
|
|
|
* Nested Validation
Added support for a plain validate attribute on a struct's field to
imply that validate() should be called on it with results being merged.
Validation errors are now keyed with a string that indicates the path to
the invalid field within a complex data structure. The errors themselves
also include the path to the invalid field, expressed as a vector of
strings.
Added support for option and vector fields where the wrapped values
perform nested validation.
Refactored vector wrapping for more reusable nested validation quoting.
Vector index is now more conveniently represented as an individual item
in the ValidationError's path attribute.
A few ergonomic changes to support custom (i.e. non-derived) Validate
implementations. A custom Validator implementation may either implement
the validate() method as before or implement the new
validate_path(ValidationPath) method which gives context of where the
validation is taking place in a complex data structure.
It is not necessary to implement both methods.
Refactored ValidationErrors to adopt a structure reflecting that of the
data being validated.
Instead of holding a vector of ValidationError instances for each field,
the ValidationErrors map may now include 3 different kinds of error
values representing the field, nested struct and nested vector of struct
scenarios.
Note that this implies a breaking change to the ValidationErrors map and
the "inner" method signature for accessing errors programmatically
compared to previous versions.
Added new accessor methods to the ValidationErrors type for retrieving
either field-level errors for a validated struct or all errors for the
struct and it's nested children.
The existing `inner` method provides the field-level behaviour for
backwards compatibility and has been marked as deprecated.
Documented the new associated functions of the ValidationErrors
implementation and removed unnecessary feature declaration in a test
module.
Refactored tests to use the new `field_errors` accessor method.
Updated README.md to describe nested validation behaviour.
Keats/validator#31
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
valeriansaliou-master
|
|
Signed-off-by: Valerian Saliou <valerian@valeriansaliou.name>
Derives for the ‘phone’ validator (still unsure about it)
Signed-off-by: Valerian Saliou <valerian@valeriansaliou.name>
Fix review
Merge + Add missing documented ‘credit_cards’ feature
Signed-off-by: Valerian Saliou <valerian@valeriansaliou.name>
Fix
Signed-off-by: Valerian Saliou <valerian@valeriansaliou.name>
Fix
Signed-off-by: Valerian Saliou <valerian@valeriansaliou.name>
Merge
Signed-off-by: Valerian Saliou <valerian@valeriansaliou.name>
‘credit_cards’ feature is no longer needed as per #33
Signed-off-by: Valerian Saliou <valerian@valeriansaliou.name>
|
|
Instead of using our own algorithm, I chose to use rs-card-validator.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
