Data Transfer Object (DTO)

This package provides a quick way to define structured objects (DTOs) using the JSON Schema standard.

A Data Transfer Object (DTO) is an object used to pass typed data between layers in your application, similiar in concept to Structs in C, Martin Fowler's Transfer Objects, or Value Objects.

DTOs are a helpful counterpart to the Data Accessor Object (DAO) or Repository patterns.

The functionality is similar to what is offered by the shape package.

Example

Define a PHP object using JSON Schema syntax:

<?php
class ExampleObject extends Dto\Dto
{
    protected $schema = [
        'type' => 'object',
        'properties' => [
            'a' => ['type' => 'string'],
            'b' => ['type' => 'integer']
        ],
        'additionalProperties' => false
    ];
}

Now you can instantiate and use your object:

<?php
// Assume you have included vendor/autoload.php and the above ExampleObject class
$obj = new ExampleObject();
$obj->a = "Some String";
$obj->b = 123; // this is defined as an integer, so values WILL be type-cast to integer!
$obj->c = 'Whoops, this will throw an Exception because additionalProperties are not allowed';

Or reference a JSON Schema directly:

<?php
class ExampleObject extends Dto\Dto
{
    protected $schema = [
        '$ref' => 'http://example.com/some/schema.json'
    ];
}

Possible Uses

In APIs: Consume a JSON Schema API at runtime without needing to parse data formats.
In Views: Instead of passing your view layer just any array, you can define a DTO and use type-hinting to ensure that your views will always have the data attributes they need.
For Caching: Instead of relying on your own haphazard convention, you can store and retrieve a specific DTO class from cache without having to guess which attributes or array keys are available.
Service Classes: when your service class expects to operate on a specific type of data.
Result Sets: instead of returning an array of stdClass objects or associative arrays from a database lookup, a DTO can describe the result set as well as the individual records.

TODO:

property dependencies https://spacetelescope.github.io/understanding-json-schema/reference/object.html
schema dependencies (extend the schema)
room for other versions JSON Schema (v5 is coming!)

Version History

3.2.7

Fixed validation issue when PHP classes were referenced in schemas using the $ref keyword.

3.2.6

Removed unused dependency on webmozart/json

3.2.4

Performance boost by eliminating redundant validation.

3.2.3

strval() conversion inside __toString() method: makes for easier UX when checking object properties.

3.2.2

Support for nested relative schema paths when reading JSON schemas.

3.2.1

Tests added for serialize method.

3.2.0

Includes the $baseDir and getBaseDir() methods in order to support relative paths to JSON schemas as used by the $ref keyword.

3.1.0

Includes proper support for in-line definitions and inheritance of them.

3.0.0

Integration of the JSON Schema 4 specification to drive all structure and type definitions.

2.0.0

We don't speak of version 2.

1.0.8

Fixes for anonymous hashes of DTOs injected into the constructor.
Corrected namespaces in tests.

1.0.7

Fixes for arrays of DTOs injected into the constructor as arrays.

1.0.6

Fixes for hierarchical data injected into the constructor.

1.0.5

Initial release with some grooming as documentation was added.

II-Zor-II/dto