respect-validation/tests/feature/Validators/InTest.php
Alexandre Gomes Gaigalas ec16b3d2df Refactor case sensitiveness support
This is a mid-size refactor that affects several validators.

Most prominently, the ones that had an `$identical` parameter
to deal with case sensitiveness.

This parameter was confusing, effectively making validators such
as `Contains` behave very differently for arrays versus strings.

In arrays, `$identical` meant "the same type", while it in strings
it meant "case sensitive".

That parameter was removed, and the default behavior is now to
always compare **case sensitive** and strict typing.

A document explaining how to combine other validators in order
to achieve case _insensitive_ comparisons was added.

Additionally, the `Call` validator was refactored back to be
suitable to take on the task of being a fast, quick composable
validator.

With the introduction of `Circuit`, we can shift the responsibility
of dealing with possible mismatches to the user. This kind of type
handling is demonstrated in how I refactored `Tld` to account for
the type mismatch without setting error handlers.
2026-01-30 17:11:13 +00:00

29 lines
900 B
PHP

<?php
/*
* SPDX-License-Identifier: MIT
* SPDX-FileCopyrightText: (c) Respect Project Contributors
* SPDX-FileContributor: Henrique Moody <henriquemoody@gmail.com>
*/
declare(strict_types=1);
test('Scenario #1', catchMessage(
fn() => v::in([3, 2])->assert(1),
fn(string $message) => expect($message)->toBe('1 must be in `[3, 2]`'),
));
test('Scenario #2', catchMessage(
fn() => v::not(v::in('foobar'))->assert('foo'),
fn(string $message) => expect($message)->toBe('"foo" must not be in "foobar"'),
));
test('Scenario #3', catchFullMessage(
fn() => v::in([2, '1', 3])->assert('2'),
fn(string $fullMessage) => expect($fullMessage)->toBe('- "2" must be in `[2, "1", 3]`'),
));
test('Scenario #4', catchFullMessage(
fn() => v::not(v::in([2, '1', 3]))->assert('1'),
fn(string $fullMessage) => expect($fullMessage)->toBe('- "1" must not be in `[2, "1", 3]`'),
));