Download the PHP package aegisora/json-rule without Composer

Aegisora JSON Rule

JSON Rule provides a simple, rule-based JSON validation implementation for the Aegisora ecosystem.

It is built on top of aegisora/rule-contract and follows its strict validation architecture, ensuring consistent and predictable behavior across applications.

This rule is useful for validating webhook payloads, API request bodies, configuration strings, message queue messages, and any other string that must contain well-formed JSON.

📑 Table of Contents

• Features
• Installation
• Core Concept
• Basic Usage
• Valid vs Invalid
• Validation Result
• Guardian Usage
• Real-World Examples
• Factory Methods
• Architecture
• License
• Contributing
• Support

✨ Features

• 🔹 Lightweight and dependency-free except aegisora/rule-contract
• 🔹 Validates whether a string contains well-formed JSON
• 🔹 Backed by native json_decode() and json_last_error()
• 🔹 Accepts any valid JSON value (objects, arrays, strings, numbers, booleans, null)
• 🔹 Rejects non-string input as an invalid context
• 🔹 Fully compatible with Aegisora validation pipeline
• 🔹 Strict Context → Result validation flow
• 🔹 No raw booleans — only structured results
• 🔹 Safe execution via base Rule abstraction
• 🔹 Simple factory API (create)
• 🔹 Ready to use out of the box

📦 Installation

🚀 Core Concept

This package implements a single validation rule:

• accepts a string value via Context
• checks whether the value is well-formed JSON
• returns a standardized Result

Under the hood it wraps the common boilerplate:

into a reusable rule that reports its outcome through a Result object instead of a raw boolean.

🏗️ Basic Usage

✅ Valid vs Invalid

The rule passes for any well-formed JSON value and fails for malformed input. Validation relies on the native JSON parser, so only strictly well-formed JSON is accepted.

Valid JSON

Invalid JSON

🧪 Validation Result

If the value is valid JSON, the rule returns a valid result.

$result->isValid(); // true

If the value is not valid JSON, the rule returns an invalid result.

If the context value is not a string, the rule throws:

Aegisora\RuleContract\Exceptions\InvalidRuleContextException

🔗 Guardian Usage

This rule can be used together with aegisora/guardian to build fluent validation pipelines.

If the value is not valid JSON, Guardian throws the provided domain exception.

🧭 Real-World Examples

JSON Rule is useful for validating string payloads before they are decoded or persisted.

Examples

🧩 Factory Methods

JsonRule::create();

• no arguments — creates a new rule instance

JsonRule::create()->validate($context);

• $context — Context wrapping the string value to validate

🏛️ Architecture

This package relies on aegisora/rule-contract.

Flow:

1. validate() is called
2. Context is passed in
3. The string value is extracted from context (non-strings raise InvalidRuleContextException)
4. The value is decoded with json_decode()
5. json_last_error() is checked
6. Result is returned — valid on success, invalid with the json_rule code on failure

All logic is safely handled by Rule contract.

⚖️ 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.