somnambulist/value-objects

This package is abandoned and no longer maintained. The author suggests using the somnambulist/domain package instead.

A simple value-object implementation for use in Entities. Includes a couple of basic types.

1.4.0 2019-01-03 17:45 UTC

Requires

• php: >=7
• ext-mbstring: *
• beberlei/assert: ~3.0
• eloquent/enumeration: ~5.1
• somnambulist/collection: ~2.1

Requires (Dev)

• phpunit/phpunit: ~7.0
• ramsey/uuid: ~3.7

Suggests

• giggsey/libphonenumber-for-php: *
• propaganistas/laravel-phone: *

MIT

• Dave Redfern

• entities
• ddd
• value objects
• domain events

README

This repository has been archived. Please update to the combined package.s

Value Objects Library

Value Objects (VOs) are Immutable domain objects that represent some value in your domain model but without a thread of continuous identity i.e. their identity is through their properties. VOs allow your entities to encapsulate properties and provide type safety.

This library provides an abstract base class that provides a basic equality test and foundation for your VOs along with a couple of basic types. As VOs form part of YOUR domain, you should implement the VOs that you need for your domain, following your domain naming (e.g. if you do not call an email address an EmailAddress then create your own VO for that purpose).

VOs should be self-validating during construction. For this purpose, the Assertion library by Benjamin Eberlei is used, however you may wish to use another or filter_var() etc directly.

If you see something missing or have suggestions for other methods, submit a PR or ticket.

Requirements

• PHP 7+
• mb_string
• beberlei/assert
• eloquent/enumeration
• somnambulist/collection

Installation

Install using composer, or checkout / pull the files from github.com.

• composer require somnambulist/value-objects

Usage

Extend the abstract value object and implement the single required method toString(). The default equality method (equals()) uses reflection on the VO properties and compares them directly - only between VO types.

For example:

use Assert\Assert;
use Somnambulist\ValueObjects\AbstractValueObject;

class Uuid extends AbstractValueObject
{

    /**
     * @var string
     */
    private $uuid;

    /**
     * Constructor.
     *
     * @param string $uuid
     */
    public function __construct(string $uuid)
    {
        Assert::that($uuid, null, 'uuid')->notEmpty()->uuid();

        $this->uuid = $uuid;
    }

    /**
     * @return string
     */
    public function toString(): string
    {
        return $this->uuid;
    }
}

$uuid = new Uuid(\Ramsey\Uuid\Uuid::uuid4());

Usage with Doctrine

These VOs may be used with Doctrine as Embeddable objects - however if you allow the VO to be null, it will be instantiated empty so your methods / toString() should handle that case e.g.:

A User has a nullable Profile VO, when Doctrine hydrates the User, the Profile VO will also be hydrated but empty, so if the Profile has a nickname() or avatar() method, these must support returning null and your toString() method must cast null to a string to avoid type errors.

Links

• Doctrine
• Enumeration Bridge