Download the PHP package acgrid/assert without Composer

Assert

Travis Status:

This is a personal forked version. It has been rewritten so that all the components can be overridden in user land. Also, this fork will ONLY work on PHP 5.5 or above due to class name constants.

A simple php library which contains assertions and guard methods for input validation (not filtering!) in business-model, libraries and application low-level code. The library can be used to implement pre-/post-conditions on input data.

Idea is to reduce the amount of code for implementing assertions in your model and also simplify the code paths to implement assertions. When assertions fail, an exception is thrown, removing the necessity for if-clauses in your code.

The library is not using Symfony or Zend Validators for a reason: The checks have to be low-level, fast, non-object-oriented code to be used everywhere necessary. Using any of the two libraries requires instantiation of several objects, using a locale component, translations, you name it. Its too much bloat.

Installation

Using Composer:

Example usages

Real time usage with Azure Blob Storage:

NullOr helper

A helper method (Assertion::nullOr*) is provided to check if a value is null OR holds for the assertion:

All helper

The Assertion::all* method checks if all provided values hold for the assertion. It will throw an exception of the assertion does not hold for one of the values:

\acgrid\Assert\that() Chaining

Using the static API on values is very verbose when checking values against multiple assertions. Starting with 2.0 of Assert there is a much nicer fluent API for assertions, starting with \acgrid\Assert\that($value) and then receiving the assertions you want to call on the fluent interface. You only have to specify the $value once.

There are also two shortcut function \acgrid\Assert\thatNullOr() and \acgrid\Assert\thatAll() enabling the "nullOr" or "all" helper respectively.

Lazy Assertions

There are many cases in web development, especially when involving forms, you want to collect several errors instead of aborting directly on the first error. This is what lazy assertions are for. Their API works exactly like the fluent \acgrid\Assert\that() API, but instead of throwing an Exception directly, they collect all errors and only trigger the exception when the method verifyNow() is called on the acgrid\Assert\SoftAssertion object.

The method that($value, $propertyPath) requires a property path (name), so that you know how to differentiate the errors afterwards.

On failure verifyNow() will throw an exception acgrid\Assert\\LazyAssertionException with a combined message:

The following 3 assertions failed:
1) foo: Value "10" expected to be string, type integer given.
2) bar: Value "<NULL>" is empty, but non empty value was expected.
3) baz: Value "string" is not an array.

You can also retrieve all the AssertionFailedExceptions by calling getErrorExceptions(). This can be useful for example to build a failure response for the user.

List of assertions

Remember: When a configuration parameter is necessary, it is always passed AFTER the value. The value is always the first parameter.

Exception & Error Handling

If any of the assertions fails a acgrid\Assert\AssertionFailedException is thrown. You can pass an argument called to any assertion to control the exception message. Every exception contains a default message and unique message code by default.

acgrid\Assert\AssertionFailedException is just an interface and the default implementation is acgrid\Assert\InvalidArgumentException which extends the SPL InvalidArgumentException. You can change the exception being used on a package based level.

Your own Assertion class

To shield your library from possible bugs, misinterpretations or BC breaks inside Assert you should introduce a library/project based assertion subclass, where you can override the exception thrown as well. In addition, you can override the acgrid\Assert\Assertion::stringify() method to provide your own interpretations of the types during error handling.

And you can configure which static class will be called for the function helpers:

Contributing

Please see CONTRIBUTING for more details.