Download the PHP package good-system/laravel-model-history without Composer
On this page you can find all versions of the php package good-system/laravel-model-history. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 laravel-model-history
Laravel Model History
Installation
Usage
Use Generic ModelObserver
If model history logging/recording for "created" and "updated" are the only things you need to do in a model observer, simply add something like the following to your service provider class:
And two model actions will be logged in database table model_history
- new donation created
- donation updated
Use Trait ModelChangeEventTraits
If your model observer needs to observe additional model events, but for "created" and "updated" events, model history logging/recording is the only thing needed, trait ModelChangeEventTraits could be added to observer class, like this
Use ModelFieldHistory model static methods directly
Model class ModelFieldHistory provides two additional methods
forModelCreated()- record newly created modelforFieldChanges()- record changes made to the model
If your model observer's "created" or "updated" event needs to do history logging/recording, plus other things, these two methods can be called from the observer directly, like this:
Other Usage
No other usage at this point. Note that the database table is not limited to accommodate these two changes.
