mirror of
https://github.com/Respect/Validation.git
synced 2026-03-14 22:35:45 +01:00
d4605f4493Before this change, querying validation results required knowing the exact path to a specific result node—including numeric indices for array elements (e.g., `items.1.email`). This made it impractical to locate the first failing result in dynamic collections where the failing index is not known ahead of time. Wildcard segments (`*`) allow matching any single path component, so patterns like `items.*`, `*.email`, or `data.*.value` will traverse the result tree and return the first node whose path matches. This is particularly valuable when validating arrays of items with `each()`, because consumers can now ask "give me the first failure under items" without iterating manually. The implementation replaces the previous flat `array_find` lookup with a recursive depth-first traversal that, when a wildcard is present, compares each node's full path against the pattern using segment-level matching. Non-wildcard lookups continue to use exact array equality, so there is no behavioral change for existing callers. Assisted-by: Claude Code (claude-opus-4-6) |
||
|---|---|---|
| .. | ||
| messages | ||
| validators | ||
| .pages | ||
| case-sensitiveness.md | ||
| comparable-values.md | ||
| comparing-empty-values.md | ||
| configuration.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 | ||