Download the PHP package cebe/yii2-lifecycle-behavior without Composer
On this page you can find all versions of the php package cebe/yii2-lifecycle-behavior. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download cebe/yii2-lifecycle-behavior
More information about cebe/yii2-lifecycle-behavior
Files in cebe/yii2-lifecycle-behavior
Package yii2-lifecycle-behavior
Short Description Define the lifecycle of a model by defining allowed satus changes in terms of a state machine.
License MIT
Homepage https://github.com/cebe/markdown#readme
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package yii2-lifecycle-behavior
Yii 2 lifecycle behavior
Define the lifecycle of a model by defining allowed status changes in terms of a state machine.
Installation
This is an extension for the Yii 2 PHP framework.
Installation is recommended to be done via composer by running:
composer require cebe/yii2-lifecycle-behaviorAlternatively you can add the following to the require section in your composer.json manually
and run composer update afterwards:
Usage
You can add the behavior to an ActiveRecord class. It does not work with yii\base\Model
because it relies on the old-attribute feature which is only available in active record.
You can add the behavior to the model by creating a behaviors() method if there is none yet, or
add it to the list of exising behaviors.
The following example shows how to define the allowed status changes:
The above state transitions can be visualized as the following state machine:
Status field validation
By default, the behavior will validate the status attribute of the record, when validate() or save() is called
and add a validation error in case state has changed in a way that is not allowed.
- The attribute to validate can be configured by setting the
statusAttributeproperty of the behavior. - The error message can be configured by setting the
validationErrorMessageproperty of the behavior. The place holders{old}and{new}are being replaced with the corresponding status values.
Program flow validation
The behavior may also be used to validate status changes in program flow. This is different to user input validation as described above, because program flow will be aborted by an exception in this case. For user input, the recipient of the error message is the user, when status is not changed by the user, the recipient of the error is the developer.
Configuring different validation methods
By default status field is validated both, on validation and on update. To disable one of the methods, you may configure
the $events propery, which is by default:
