Download the PHP package aegisora/numeric-range-rule-guardian without Composer

Aegisora Numeric Range Rule Guardian

Numeric Range Rule Guardian provides simple shortcuts for ensuring a numeric value falls within an expected range using aegisora/guardian and aegisora/numeric-range-rule.

It is designed for cases where you want to quickly check whether a value is greater than, less than, or between given bounds without manually creating validation pipelines.

This package is built on top of:

• aegisora/guardian
• aegisora/numeric-range-rule

✨ Features

• 🔹 Simple shortcut API for NumericRangeRule
• 🔹 Validates lower bounds (checkGreaterThan, checkGreaterThanOrEqualTo)
• 🔹 Validates upper bounds (checkLessThan, checkLessThanOrEqualTo)
• 🔹 Validates ranges with inclusive/exclusive bounds (checkBetween, checkBetweenExclusive, checkBetweenMinExclusive, checkBetweenMaxExclusive)
• 🔹 Works with integers, floats and numeric strings
• 🔹 Uses aegisora/guardian internally
• 🔹 Uses aegisora/numeric-range-rule internally
• 🔹 Supports custom validation exceptions
• 🔹 Fully compatible with the Aegisora ecosystem
• 🔹 Ready to use out of the box

📦 Installation

🚀 Core Concept

This package wraps the common validation flow:

into a dedicated shortcut class:

Instead of manually creating NumericRangeRule and passing it to Guardian, you can use NumericRangeRuleGuardian directly.

🏗️ Basic Usage

🧩 Usage with Custom Exception

You may provide your own exception for validation failure.

If the value is out of the range, the provided exception will be thrown.

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

🧪 Example in Application Service

🚨 Exceptions

This package does not define its own exception types. All errors are raised by the underlying aegisora/guardian package.

Both exceptions extend the abstract base class Aegisora\Guardian\Exceptions\GuardianException, so you can catch every validation error with a single catch:

GuardianValidationException

Thrown when validation fails and no custom exception is provided.

GuardianExecutingRuleException

Thrown when the underlying rule execution fails, for example when the checked value is not numeric.

Aegisora\Guardian\Exceptions\GuardianExecutingRuleException

🧩 API

All methods share the same contract: they return void and communicate results through exceptions only — nothing is returned on success and an exception is thrown on failure:

• GuardianValidationException — validation failed and no custom exception was provided
• GuardianExecutingRuleException — the underlying rule failed to execute (e.g. the value is not numeric)
• the provided custom exception — validation failed and a custom exception was passed

Each method also throws Aegisora\RuleContract\Exceptions\InvalidRuleContextException when the range is configured with invalid bounds (a non-numeric bound, $min greater than $max, or equal bounds where at least one side is exclusive).

NumericRangeRuleGuardian::checkGreaterThan()

Valid when $value > $min.

NumericRangeRuleGuardian::checkGreaterThanOrEqualTo()

Valid when $value >= $min.

NumericRangeRuleGuardian::checkLessThan()

Valid when $value < $max.

NumericRangeRuleGuardian::checkLessThanOrEqualTo()

Valid when $value <= $max.

NumericRangeRuleGuardian::checkBetween()

Valid when $min <= $value <= $max (both bounds inclusive).

NumericRangeRuleGuardian::checkBetweenExclusive()

Valid when $min < $value < $max (both bounds exclusive).

NumericRangeRuleGuardian::checkBetweenMinExclusive()

Valid when $min < $value <= $max (lower bound exclusive, upper bound inclusive).

NumericRangeRuleGuardian::checkBetweenMaxExclusive()

Valid when $min <= $value < $max (lower bound inclusive, upper bound exclusive).

Common parameters:

• $value (mixed) — value to validate; considered valid when it is numeric and satisfies the configured range
• $min / $max (numeric) — range bounds
• $exception (?\Throwable, default null) — optional custom exception thrown on validation failure

Example:

With custom exception:

🏛️ Architecture

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

Flow:

1. A NumericRangeRuleGuardian::check*() method is called
2. The matching NumericRangeRule::create*() rule is created
3. Guardian executes the rule
4. If validation succeeds, execution continues normally
5. If validation fails, custom exception or GuardianValidationException is thrown
6. If rule execution fails, GuardianExecutingRuleException is thrown

Internal flow:

🔗 Related Packages

• aegisora/guardian — validation execution orchestrator
• aegisora/numeric-range-rule — rule-based numeric range validation
• 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.