library object-migration

evispa/object-migration

Migrations between object versions, configurable via annotations.

Object migration library

Build Status: , _(*1)

Overview

Migrate objects to different versions based on version annotations., _(*2)

For example, let's say we have two class versions, the second one modifies public field name from "slug" to "id":, _(*3)

class V1
{
    public $slug;
}

class V2
{
    public $id;
}

We can then decorate these classes with version annotations, and create migration method to the new version:, _(*4)

use Evispa\ObjectMigration\Annotations as Api;

/**
 * @Api\Version("object.v1")
 */
class V1
{
    public $slug;
}

/**
 * @Api\Version("object.v2")
 */
class V2
{
    public $id;

    /**
     * @Api\Migration(from="V1")
     */
    public static function fromV1(V1 $other, $options) {
        $obj = new self();

        $obj->id = $other->slug;

        return $obj;
    }
}

Use VersionConverter tool to check object version or migrate object to another available version:, _(*5)

use Doctrine\Common\Annotations\AnnotationReader;
use Evispa\ObjectMigration\VersionReader;
use Evispa\ObjectMigration\VersionConverter;

$converter = new VersionConverter(new VersionReader(new AnnotationReader()), 'V2');

// create v1 object

$v1 = new V1();
$v1->slug = "TEST";

// migrate to another version

$v2 = $converter->migrateFrom($v1);

$this->assertTrue($v2 instanceof V2); // true
$this->assertEquals("TEST", $v2->id); // true

Requirements

This library will use: * doctrine/annotations for annotation parsing * clue/graph for version migrations search, _(*6)

Installation

This library can be easily installed via composer, _(*7)

composer require evispa/object-migration

or just add it to your composer.json file directly., _(*8)