Download the PHP package aegisora/emptiness-rule-guardian without Composer

Aegisora Emptiness Rule Guardian

Emptiness Rule Guardian provides a simple shortcut for emptiness validation using aegisora/guardian and aegisora/emptiness-rule.

It is designed for cases where you want to quickly check whether a value is empty or is not empty, without manually building an EmptyRule / NotEmptyRule and a validation pipeline by hand.

This package is built on top of:

• aegisora/guardian
• aegisora/emptiness-rule

✨ Features

• 🔹 Simple shortcut API for EmptyRule and NotEmptyRule
• 🔹 Validates that a value is empty via checkEmpty()
• 🔹 Validates that a value is not empty via checkNotEmpty()
• 🔹 Works with scalars, arrays and countable objects
• 🔹 Uses aegisora/guardian internally
• 🔹 Uses aegisora/emptiness-rule internally
• 🔹 Supports a custom validation exception
• 🔹 Keeps rule execution errors separated from validation errors
• 🔹 Fully compatible with the Aegisora ecosystem
• 🔹 Ready to use out of the box

📦 Installation

🚀 Core Concept

This package wraps the common emptiness validation flow:

into a dedicated shortcut class:

Instead of manually creating an EmptyRule / NotEmptyRule and passing it to Guardian, you can use EmptinessRuleGuardian directly.

🏗️ Basic Usage

checkEmpty() passes when $value is empty, and fails otherwise.

checkNotEmpty() passes when $value is not empty, and fails otherwise.

✅ How the emptiness check works

A value is considered empty when it is null, an empty string, an empty array or an empty countable object. Every other value — including 0, 0.0, false and non-countable objects — is considered not empty:

checkNotEmpty() is the exact inverse — it passes for every value listed above as fails and fails for every value listed as passes.

⚠️ A resource cannot be evaluated for emptiness. Passing a resource raises a GuardianExecutingRuleException (see below) instead of a validation result.

🧩 Usage with Custom Exception

You may provide your own exception for validation failure. It must be the last argument.

If the value is empty, the provided exception will be thrown instead of GuardianValidationException.

This is useful when validation errors should have domain-specific meaning.

🧪 Example in Application Service

🚨 Exceptions

The package raises validation-related exceptions, all delegated to Guardian (the outcome of running the rule):

GuardianValidationException

Thrown when validation fails and no custom exception is provided.

The rule code for a failed checkEmpty() is empty_rule, and for a failed checkNotEmpty() it is not_empty_rule.

Custom exception

When a custom exception is passed as the last argument, it is thrown instead of GuardianValidationException on validation failure.

GuardianExecutingRuleException

Thrown when the underlying rule fails to execute (raises a RuleException during validation), as opposed to simply reporting an invalid result.

Emptiness cannot be determined for a resource, so passing a resource surfaces this exception instead of a validation result:

🧩 API

EmptinessRuleGuardian::checkEmpty()

Validates that $value is empty.

EmptinessRuleGuardian::checkNotEmpty()

Validates that $value is not empty.

Arguments (both methods):

• $value — the value to validate
• $exception — an optional custom \Throwable to be thrown on validation failure

The methods return void. They communicate results through exceptions only — they return nothing on success and throw on failure:

• GuardianValidationException — the emptiness check failed and no custom exception was provided
• the provided custom exception — the check failed and a custom exception was passed
• GuardianExecutingRuleException — the rule could not be executed

🏛️ Architecture

This package is a small shortcut layer over the Aegisora validation pipeline.

Flow:

1. EmptinessRuleGuardian::checkEmpty() / checkNotEmpty() is called with a value and an optional exception
2. An EmptyRule / NotEmptyRule is created (create())
3. Guardian executes the rule against the value
4. If the check passes, execution continues normally
5. If the check fails, the custom exception or GuardianValidationException is thrown
6. If the rule could not be executed, GuardianExecutingRuleException is thrown

Internal flow:

🔗 Related Packages

• aegisora/guardian — validation execution orchestrator
• aegisora/emptiness-rule — empty and not empty rules
• aegisora/rule-contract — base rule contract and validation result architecture

⚖️ License

This package is open-source and licensed under the MIT License. See the LICENSE for details.

🌱 Contributing

Contributions are welcome and greatly appreciated!. See the CONTRIBUTING for details.

🌟 Support

If you find this project useful, please consider giving it a star on GitHub!

It helps the project grow and motivates further development.