kmuenkel/validation-patch

Correct for various issues in Laravel Validation

1.0.2 2020-11-30 16:00 UTC

Requires

• illuminate/validation: ^7.0|^8.0

Requires (Dev)

• barryvdh/laravel-ide-helper: ^2.8
• friendsofphp/php-cs-fixer: ^2.16
• fzaninotto/faker: ^1.9
• mockery/mockery: ^1.4
• orchestra/testbench: ^5.7
• phpmd/phpmd: ^2.9
• phpunit/phpunit: ^9.4
• squizlabs/php_codesniffer: ^3.5

MIT

• Kevin Muenkel

• validation
• laravel
• fix

README

For all fixes, simply including ValidationPatch\ValidationPatchServiceProvider in your app config will allow them to take effect automatically.

Fixes

1. Dots in field names: Laravel offers the ability to escape dots in field names so that they're not mistaken for dot-delimiters for nested arrays. However, this did not apply to field references within in rules such as required_with or exclude_unless. This corrects for that.
2. Forward slashes in field names: Due to a parsing errors, field names that had forward slashes, such as URI claims, would cause an error. These are now supported.
3. required only active if parent exists: If a nested array element carried an incarnation of the required rule, it would be executed even if the parent element were optional. With this package, nested requirements only fire if the parent exists.
4. Custom Rule Message Placeholders: Allow Illuminate\Contracts\Validation\Rule::message() output to be respected when aliased via Illuminate\Support\Facades\Validator::extend(). Also allow those messages to contain placeholders such as "attribute" or ":input".