mirror of
https://github.com/Respect/Validation.git
synced 2024-06-03 06:12:17 +02:00
24885e4a5f
Because we have the Key and Property rules, the KeyNested is redundant, although it's a helpful shortcut. The real problem is dealing with messages and templates because the structure of the validator needs to match the structure of the rule. When using the `getMessages()` method from the exception we throw in `assert()`, we get a flat structure, which is often not the intended structure. The KeyNested rule is cool, but it adds some complexity to the codebase that I'm unwilling to deal with. It's not nice to remove a rule, especially because I know people use it, but it's for the best. I'm trying to keep the codebase small, so hopefully, it will get easier to maintain. Signed-off-by: Henrique Moody <henriquemoody@gmail.com> |
||
|---|---|---|
| .github | ||
| bin | ||
| data/domain/public-suffix | ||
| docs | ||
| library | ||
| tests | ||
| .docheader | ||
| .gitattributes | ||
| .gitignore | ||
| .readthedocs.yaml | ||
| CHANGELOG.md | ||
| composer.json | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| mkdocs.yml | ||
| phpcs.xml.dist | ||
| phpstan.neon.dist | ||
| phpunit.xml.dist | ||
| README.md | ||
Respect\Validation
The most awesome validation engine ever created for PHP.
- Complex rules made simple:
v::numericVal()->positive()->between(1, 255)->validate($input). - Granularity control for advanced reporting.
- More than 150 (fully tested) validation rules.
- A concrete API for non fluent usage.
Learn More: