Download the PHP package stojankukrika/versionable without Composer

Versionable

Tnx Original project for start point and this project start point. This project started as fork but because original user didn't update it we will make it better.

Easy to use Model versioning for Laravel

Keep track of all your model changes and revert to previous versions of it.

Installation

In order to add Versionable to your project, just add

"stojankukrika/versionable": "~1.0"

to your composer.json. Then run composer install or composer update.

Or run composer require stojankukrika/versionable if you prefere that.

Publish configuration and migrations using the vendor:publish command.

Run the migrations to create the "versions" table that will hold all version information.

bash php artisan migrate --path=vendor/mpociot/versionable/src/migrations php artisan migrate

Usage

Let the Models you want to set under version control use the VersionableTrait.

That's it!

Every time you update your model, a new version containing the previous attributes will be stored in your database.

All timestamps and the optional soft-delete timestamp will be ignored.

Exclude attributes from versioning

Sometimes you don't want to create a version every time an attribute on your model changes. For example your User model might have a last_login_at attribute. I'm pretty sure you don't want to create a new version of your User model every time that user logs in.

To exclude specific attributes from versioning, add a new array property to your model named dontVersionFields.

Maximum number of stored versions

You can control the maximum number of stored versions per model. By default, there will be no limit and all versions will be saved. Depending on your application, this could lead to a lot of versions, so you might want to limit the amount of stored versions.

You can do this by setting a $keepOldVersions property on your versionable models:

Retrieving all versions associated to a model

To retrieve all stored versions use the versions attribute on your model.

This attribute can also be accessed like any other Laravel relation, since it is a MorphMany relation.

Getting a diff of two versions

If you want to know, what exactly has changed between two versions, use the version model's diff method.

The diff method takes a version model as an argument. This defines the version to diff against. If no version is provided, it will use the current version.

The result will be an associative array containing the attribute name as the key, and the different attribute value.

Revert to a previous version

Saving versions is pretty cool, but the real benefit will be the ability to revert to a specific version.

There are multiple ways to do this.

Revert to the previous version

You can easily revert to the version prior to the currently active version using:

Revert to a specific version ID

You can also revert to a specific version ID of a model using:

Disable versioning

In some situations you might want to disable versioning a specific model completely for the current request.

You can do this by using the disableVersioning and enableVersioning methods on the versionable model.

Use different version table

Some times we want to have models versions in differents tables. By default versions are stored in the table 'versions', defined in StojanKukrika\Versionable\Version::$table.

To use a different table to store version for some model we have to change the table name. To do so, create a model that extends StojanKukrika\Versionable\Version and set the $table property to another table name.

In the model that you want it use this specific versions table, use the VersionableTrait Trait and add the property $versionClass with value the specific version model.

And do not forget to create a migration for this versions table, exactly as the default versions table.

License

Versionable is free software distributed under the terms of the MIT license.