Download the PHP package mixteer/reshi without Composer

Reshi - facilitating assertive programming

"If It Can't Happen, Use Assertions to Ensure That It Won't" -- A. Hunt and D. Thomas in The Pragmatic Programmer.

Reshi is an assertion library that it meant to check constraints you impose on say function input parameters. The idea behind it is that of assertive programming as found in Section 23, Chapter 4 of the book The Pragmatic Programmer.

You use Reshi to make sure that event that you think will never occur doesn't cause damage in case it does occur. See Section 22 Dead programs tell no lies of the same chapter.

Install

The library is available on packagist and installable via composer.

Concepts

The 3 main concepts about the why and how of this library are derived from The Pragmatic Programmer in Chapter 4:

1. Assertive programming - you use assertions to make sure things that shouldn't normally happen are guarded against just in case they do happen.

2. Dead programs tell no lies - if an assertion fails, the library triggers a E_USER_ERROR error which ends the program immediately. You'll have an error handler which should log this error as it will contain the details of which assertion failed and details like file name and line number.

3. Use exceptions for exceptional cases - the library doesn't throw an exception when the assertion fails simply to help avoid someone catching the exception, doing nothing with it and hence the program might continue. Yes, errors can be converted into exceptions but going to all that trouble assumes you have a good idea and fair reason for doing so. Note that while assertions help guard against rare bad events, those are not part of your business logic so use of exceptions here is not a good idea. But when the library methods are given wrong parameters, the will emit exceptions because that's part of their business logic.

Usage

Using the library is fairly simple:

It is very likely that you'll use this method in a class and $this->assertThat will pause a problem since PHP will look for the method assertThat in the current class.
There are a number of ways to go around this problem:

• Helper method:
  Create a helper method that is returns an instance of the Assertion and use it. The problem with this approach is that it creates many Assertion objects. So this is solution is generally not recommended.

• Helper method with caching:
  We can also cache the result of the previous function call and reuse the object that was previously constructed. This is much better since we'll reuse the same assertion object between multiple calls. Notice that we take care to change the parameter the assertion is working with else it will reuse the old one.

• Implement __call:
  In this approach, you implement the magic method __call to intercept "the missing method", execute it which then returns the result we want.

For developers heavily using domain models, the __call method would ideally go on a Layer supertype so as to avoid duplication.

• Create a namespaced function:
  Let's assume again you're using a Layer Supertype. Instead of implementing the __call method, you'd create a function in the same class as the Layer Supertype class and import it (as of PHP 5.6+).

Usage go as this:

Assertions

This is not an exhaustive list of assertions yet but we re adding more in this documentation and in the code as fast as we can.

• assertIsTrue($param): Stops the execution of the program if $param is false.
  Method: isTrue().
  Static example: Assertion::assertIsTrue(true); Instance example: $assertThat(true)->isTrue();

• assertIsFalse($param): Stops the execution of the program if $param is true.
  Method: isFalse().
  Static example: Assertion::assertIsFalse(false); Instance example: $assertThat(true)->isFalse();

• assertIsInstanceOf($object, string $klass): Stops the execution of the program if $object is not an instance of $klass.
  Method: isInstanceOf(string $klass).
  Static example: Assertion::assertIsInstanceOf($user, 'User'); Instance example: $assertThat($user)->isInstanceOf('User');

• assertIsNotInstanceOf($object, string $klass): Stops the execution of the program if $object is an instance of $klass.
  Method: isNotInstanceOf(string $klass).
  Static example: Assertion::assertIsNotInstanceOf($user, 'User'); Instance example: $assertThat($user)->isNotInstanceOf('User');

For now, looking into the Assertion.php file will show all the assertions. Bellow is an undocumented list of the assertions but we'll documenting them slowly.

• assertIsType($param, string $type)
• assertIsBool($param)
• assertIsInt($param)
• assertIsFloat($param)
• assertIsString($param)
• assertIsArray($param)
• assertIsObject($param)
• assertIsResource($param)
• assertIsCallable($param)
• assertIsNull($param)
• assertIsEmpty($param)
• assertHasCount($array)
• assertEquals($operandOne, $operandTwo)
• assertIsGreaterThan($operandOne, $operandTwo)
• assertIsGreaterThanOrEqualTo($operandOne, $operandTwo)
• assertIsLessThan($operandOne, $operandTwo)
• assertIsLessThanOrEqualTo($operandOne, $operandTwo)
• assertSame($operandOne, $operandTwo)
• assertFileExists(string $file)
• assertHasSameContent(string $fileOne, string $fileTwo)
• assertEqualsFile(string $string, string $file)
• assertStartsWith(string $needle, string $string)
• assertEndsWith(string $needle, string $string)
• assertArrayContains($needle, array $haystack)
• assertArrayContainsOnly(string $type, array $haystack)
• assertArrayContainsOnlyInstancesOf(string $klass, array $haystack)
• assertArrayHasKey($key, array $haystack)
• assertObjectHasAttribute(string $attribute, object $object)

Each of those static methods has an instance counterpart (which might not have the same "signature" and a negation counterpart as well.

Adding new assertions

Reshi allows you to create new assertions of your own.
To add a new assertion, you just implement the interface ReshiConstraint. Follow the example bellow to see how this is done.

• Implement the ReshiConstraint interface:
  This interface requires two method: evaluate() which will be called by the static method assertThat and getName() which must return a string whose content is the name of the constraint. This name is included in the failure message to allow the developer to identify which assertion failed.

• Extend the Assertion class:
  You might want to extend the Assertion class so that you can have a unified assertion class with all th existing methods from the library accessible.

Now you can use MyAssertion instead of Assertion and have access to both your assertions and the existing assertions.

About

Requirements

Reshi has been test on PHP 5.5 but all the features should work from PHP 5.3 - see composer.json. Testing on other platforms is welcome. Email one the authors bellow.

Bugs and feature requests

All bugs and feature requests are tracked on GitHub.

Contributing

Please send us a pull request.

Tests

To run tests:

Authors

Ntwali Bashige - [email protected] - http://twitter.com/nbashige
Armando Sudi - https://github.com/ArmandoSudi

License

Reshi is licensed under MIT, see LICENSE file.

Acknowledgment

The assertions are inspired from PHPUnit.