respect-validation/tests/feature/Issues/Issue425Test.php
Henrique Moody 562d98d805
Refactor the NotEmpty rule
Since we have the ability to use `not` as a prefix, having rules that
validate negative behaviour makes them a bit inflexible, verbose, and
harder to understand.

This commit will refactor the `NotEmpty`, and rename it to `Falsy`. It
will no longer trim strings, because Blank does a much better job at it;
it only simulates the behaviour of PHP’s native `empty()` function.

Because `Falsy`, `Blank`, and `Undef` have similar behaviour, I created
a page to demonstrate the difference and show when the user should use
one or the other.

Assisted-by: Cursor (claude-4.5-opus-high)
2025-12-29 12:48:35 +01:00

21 lines
772 B
PHP

<?php
/*
* Copyright (c) Alexandre Gomes Gaigalas <alganet@gmail.com>
* SPDX-License-Identifier: MIT
*/
declare(strict_types=1);
test('https://github.com/Respect/Validation/issues/425', catchAll(
function (): void {
$validator = v::create()
->key('age', v::intType()->notBlank()->noneOf(v::stringType(), v::arrayType()))
->key('reference', v::stringType()->notBlank()->lengthBetween(1, 50));
$validator->assert(['age' => 1]);
},
fn(string $message, string $fullMessage, array $messages) => expect()
->and($message)->toBe('`.reference` must be present')
->and($fullMessage)->toBe('- `.reference` must be present')
->and($messages)->toBe(['reference' => '`.reference` must be present']),
));