PHPackages                             mistralys/application-utils-result-handling - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. mistralys/application-utils-result-handling

ActiveLibrary

mistralys/application-utils-result-handling
===========================================

Classes used to store information on the results of application operations.

1.0.1(1y ago)130.7k—6.4%1MITPHPPHP >=7.4

Since Jan 13Pushed 1y ago1 watchersCompare

[ Source](https://github.com/Mistralys/application-utils-result-handling)[ Packagist](https://packagist.org/packages/mistralys/application-utils-result-handling)[ RSS](/packages/mistralys-application-utils-result-handling/feed)WikiDiscussions main Synced 1mo ago

READMEChangelog (2)Dependencies (4)Versions (3)Used By (1)

AppUtils - Result handling
==========================

[](#apputils---result-handling)

Collection of classes used to store information on the results of application operations.

This is part of the [AppUtils project](https://github.com/Mistralys/application-utils).

Features
========

[](#features)

- Store detailed status messages.
- Store success as well as error or warning messages.
- Store a single result or a collection of results.
- Ideal to collect validation messages, for example.
- Recognize results easily with numeric codes.
- Extend the classes to add custom methods.

Requirements
============

[](#requirements)

- PHP 7.4 or higher
- [Composer](https://getcomposer.org/)

Usage
=====

[](#usage)

Single possible result
----------------------

[](#single-possible-result)

If an operation can only have a single possible result state, you can use the `OperationResult` class.

```
use function AppUtils\operationResult

const ERROR_FILE_NOT_FOUND = 1;

function doSomething() : OperationResult
{
    // Create a new result object using the global function
    $result = operationResult();

    if(!file_exists('waldo.txt')) {
        return $result->makeError(
            'The waldo file could not be found :(',
            ERROR_FILE_NOT_FOUND
        );
    }

    return $result;
}

$result = doSomething();

if(!$result->isValid()) {
    echo $result;
}
```

> NOTE: The `isValid()` method returns `true` if no state was set, or the state is of the success type.

Collection of results
---------------------

[](#collection-of-results)

### Introduction

[](#introduction)

If an operation can have multiple possible result states, like a validation operation, for example, you can use the result collection class.

Every call to `makeError()`, `makeWarning()` or `makeSuccess()`will add a new result instance to the collection.

> All result types are stored in the collection, so it is important to note that both failed and successful operations can be tracked.

### Quick Start

[](#quick-start)

```
use function AppUtils\operationCollection;
use AppUtils\OperationResult_Collection;

const VALIDATION_ERROR_NAME_TOO_SHORT = 1;
const VALIDATION_WARNING_NOT_RECOMMENDED_LENGTH = 2;

function validateSomething() : OperationResult_Collection
{
    $collection = operationCollection();

    $collection->makeError(
        'The name must be at least 5 characters long',
        VALIDATION_ERROR_NAME_TOO_SHORT
    );

    $collection->makeWarning(
        'The name must be at most 50 characters long',
        VALIDATION_WARNING_NOT_RECOMMENDED_LENGTH
    )

    return $collection;
}

$collection = validateSomething();

if(!$collection->isValid()) {
     $results = $collection->getResults();
     // do something with the results
}
```

> NOTE: The `isValid()` method returns `true` if none of the results in the collection are of the error or warning type.

### Accessing the results

[](#accessing-the-results)

Accessing results is made to be as easy as possible, with many different ways to get the information you need.

```
use function AppUtils\operationCollection;

$collection = operationCollection();

// Get all results in the order they were added
$results = $collection->getResults();

// Get all errors
$errors = $collection->getErrors();

// Get all warnings
$warnings = $collection->getWarnings();

// Get all successes
$successes = $collection->getSuccesses();

// Get all notices
$notices = $collection->getNotices();

// Check if the collection contains any result of a specific type
if($collection->isError()) {}
if($collection->isWarning()) {}
if($collection->isSuccess()) {}
if($collection->isNotice()) {}

// Check if the collection contains a specific result code
if($collection->containsCode(1)) {
    // do something
}

// Get all unique result codes
$codes = $collection->getCodes();
```

### Counting results

[](#counting-results)

All result types can be counted individually, and the total number of results can be counted as well.

```
use function AppUtils\operationCollection;

$collection = operationCollection();

// Count the total number of results
$all = $collection->countResults();
$errors = $collection->countErrors();
$warnings = $collection->countWarnings();
$successes = $collection->countSuccesses();
$notices = $collection->countNotices();

```

Extend the result classes
-------------------------

[](#extend-the-result-classes)

Both the `OperationResult` and collection classes are designed to be extended, so you can add your own custom methods to them.

The most common use for this is to correctly document the result subject's type:

```
use AppUtils\OperationResult;

/**
 * @method MyOperation getSubject()
 */
class MyOperationResult extends OperationResult
{
    public function __construct(MyOperation $subject)
    {
        parent::__construct($subject);
    }
}
```

###  Health Score

32

—

LowBetter than 72% of packages

Maintenance41

Moderate activity, may be stable

Popularity30

Limited adoption so far

Community9

Small or concentrated contributor base

Maturity39

Early-stage or recently created project

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~0 days

Total

2

Last Release

490d ago

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/8895528?v=4)[Mistralys](/maintainers/Mistralys)[@Mistralys](https://github.com/Mistralys)

---

Top Contributors

[![Mistralys](https://avatars.githubusercontent.com/u/8895528?v=4)](https://github.com/Mistralys "Mistralys (18 commits)")

---

Tags

phpresult-collectionresultset

###  Code Quality

TestsPHPUnit

Static AnalysisPHPStan

Type Coverage Yes

### Embed Badge

![Health badge](/badges/mistralys-application-utils-result-handling/health.svg)

```
[![Health](https://phpackages.com/badges/mistralys-application-utils-result-handling/health.svg)](https://phpackages.com/packages/mistralys-application-utils-result-handling)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)