mirror of
https://github.com/Respect/Validation.git
synced 2026-03-16 07:15: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)
25 lines
895 B
PHP
25 lines
895 B
PHP
<?php
|
|
|
|
/*
|
|
* Copyright (c) Alexandre Gomes Gaigalas <alganet@gmail.com>
|
|
* SPDX-License-Identifier: MIT
|
|
*/
|
|
|
|
declare(strict_types=1);
|
|
|
|
date_default_timezone_set('UTC');
|
|
|
|
test('Scenario #1', catchMessages(
|
|
fn() => v::create()
|
|
->key('username', v::lengthBetween(2, 32))->key('birthdate', v::dateTime())
|
|
->key('password', v::notBlank())
|
|
->key('email', v::email())
|
|
->assert(['username' => 'u', 'birthdate' => 'Not a date', 'password' => '']),
|
|
fn(array $messages) => expect($messages)->toBe([
|
|
'__root__' => '`["username": "u", "birthdate": "Not a date", "password": ""]` must pass all the rules',
|
|
'username' => 'The length of `.username` must be between 2 and 32',
|
|
'birthdate' => '`.birthdate` must be a valid date/time',
|
|
'password' => '`.password` must not be blank',
|
|
'email' => '`.email` must be present',
|
|
]),
|
|
));
|