respect-validation/docs/rules/Falsy.md
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

1.4 KiB

Falsy

  • Falsy()

Validates whether the given input is considered empty or falsy, similar to PHP's empty() function.

We recommend you to check Comparing empty values for more details.

v::falsy()->isValid(''); // true

Null values are empty:

v::falsy()->isValid(null); // true

Numbers:

v::falsy()->isValid(0); // true

Empty arrays:

v::falsy()->isValid([]); // true

Templates

Falsy::TEMPLATE_STANDARD

Mode Template
default {{subject}} must be falsy
inverted {{subject}} must not be falsy

Template placeholders

Placeholder Description
subject The validated input or the custom validator name (if specified).

Categorization

  • Miscellaneous

Changelog

Version Description
3.0.0 Renamed to Falsy and changed the behavior
0.3.9 Created as NotEmpty

See also: