mirror of
https://github.com/Respect/Validation.git
synced 2026-03-17 15:50:03 +01:00
No description
- PHP 99.1%
- Shell 0.9%
1915b6fff7When nested-structural validation fails, it's challenging to identify which rule failed from the main exception message. A great example is the `Issue796Test.php` file. The exception message says: host must be a string But you're left unsure whether it's the `host` key from the `mysql` key or the `postgresql` key. This commit changes that behaviour by introducing the concept of "Path." The `path` represents the path that a rule has taken, and we can use it in structural rules to identify the path of an array or object. Here's what it looks like before and after: ```diff -host must be a string +`.mysql.host` must be a string ``` Because paths are a specific concept, I added a dot (`.`) at the beginning of all paths when displaying them. I was inspired by the `jq` syntax. I also added backticks around paths to distinguish them from any other value. I didn't manage to fix a test, and I skipped it instead of fixing it because I want to make changes in how we display error messages as arrays, and it will be easier to fix it then. |
||
|---|---|---|
| .github | ||
| bin | ||
| data/domain/public-suffix | ||
| docs | ||
| library | ||
| tests | ||
| .docheader | ||
| .gitattributes | ||
| .gitignore | ||
| .readthedocs.yaml | ||
| CHANGELOG.md | ||
| codecov.yml | ||
| 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)->isValid($input). - Granularity control for advanced reporting.
- More than 150 (fully tested) validation rules.
- A concrete API for non fluent usage.
Learn More: