mirror of
https://github.com/Respect/Validation.git
synced 2026-03-15 06:45:44 +01:00
bcc60ec035
Now empty values are again allowed in FilteredArray-style validators. To solve the issue with negation, a Result attribute was added to signal indeciseveness (when a result cannot be reliably inverted). On such cases, we consider that result to be valid. For example, `v::not(v::min(v::equals(10)))` says "The lowest value of the iterable input should not be equal 10". If the input is empty, we cannot decide whether its minimum is equal to 10 or not, so the validator essentially becomes a null-op. Users that want to ensure these validators have a valid decidable target must use it in combination with `Length` or other similar validators to achieve the same result. |
||
|---|---|---|
| .. | ||
| messages | ||
| validators | ||
| .pages | ||
| case-sensitiveness.md | ||
| comparable-values.md | ||
| comparing-empty-values.md | ||
| concrete-api.md | ||
| custom-validators.md | ||
| feature-guide.md | ||
| getting-started.md | ||
| handling-exceptions.md | ||
| handling-results.md | ||
| index.md | ||
| migrating-from-v2-to-v3.md | ||
| prefixes.md | ||
| requirements.txt | ||
| validators.md | ||