mirror of
https://github.com/Respect/Validation.git
synced 2026-03-16 23:35:45 +01:00
562d98d805Since 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)
24 lines
850 B
PHP
24 lines
850 B
PHP
<?php
|
|
|
|
/*
|
|
* Copyright (c) Alexandre Gomes Gaigalas <alganet@gmail.com>
|
|
* SPDX-License-Identifier: MIT
|
|
*/
|
|
|
|
declare(strict_types=1);
|
|
|
|
test('default template', catchAll(
|
|
fn() => v::falsy()->assert('non-falsy'),
|
|
fn(string $message, string $fullMessage, array $messages) => expect()
|
|
->and($message)->toBe('"non-falsy" must be falsy')
|
|
->and($fullMessage)->toBe('- "non-falsy" must be falsy')
|
|
->and($messages)->toBe(['falsy' => '"non-falsy" must be falsy']),
|
|
));
|
|
|
|
test('inverted template', catchAll(
|
|
fn() => v::not(v::falsy())->assert(null),
|
|
fn(string $message, string $fullMessage, array $messages) => expect()
|
|
->and($message)->toBe('`null` must not be falsy')
|
|
->and($fullMessage)->toBe('- `null` must not be falsy')
|
|
->and($messages)->toBe(['notFalsy' => '`null` must not be falsy']),
|
|
));
|