Download the PHP package gazugafan/laravel-changelog without Composer
On this page you can find all versions of the php package gazugafan/laravel-changelog. 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-changelog
Laravel Model Changelogs
Database record changelogging for Laravel 5
Automatically log who did what, when, and from where. Pairs super well with laravel-temporal!
Requirements
- This has only been tested on Laravel 5.4 with PHP 7.1. Let me know if you find it works on older versions!
- Also only tested with MySQL/MariaDB. Let me know if you find it works with other databases!
- No unit tests yet.
Installation
Install via Composer...
Add the service provider to the array in ...
And add an alias to the array in ...
Overview
Changelogged tables get a new column, which relates to a new table to save details about the latest change to a record. Wrapping changes in database transactions allows multiple tables to be affected by the same change. The ID of the authenticated user is automatically logged with each change (if possible), and you can include details like notes and the interface the change took place from.
When paired with laravel-temporal, this will give you the history of every change made to a record, including who made each change and exactly what was changed.
Schema Migration
Run the following migration to create the necessary table...
You'll also need to add a column to any table you want to log changes in...
Model Setup
To make your model support changelogging, just add the trait to the model's class...
You can also set some model-specific options...
Usage
Logging changes
To start logging a change, call . You can optionally specify the interface and notes to log along with the change...
This will insert a new change into the table with a status of , and automatically fill in the authenticated user's ID if one is available. Next, start doing everything related to your change...
Whenever you a model with the trait, the ID of the change in progress will automatically be filled into the the record's .
When you're finished with your change, call . This will finalize the change by updating its status to . If the change failed for some reason, you can call to abandon the change and set its status to . Here's what the whole thing might look like...
If this looks similar to how database transactions are handled in Laravel, that's no coincidence! By default, the methods above will also wrap your change in a transaction. This means if something goes wrong during your change, the entire thing will automatically be rolled back. In other words: either the entire change happens successfully, or the entire thing fails. There's no way for just part of the change to complete. Also just like Laravel transactions, you can use the method with a closure...
If you'd like to disable the use of transactions for some reason, pass as the third parameter to ...
The authenticated user's ID is retrieved via . If you'd like to override this with your own behavior, you can pass a closure to ...
Pitfalls
- Unlike normal Laravel database transactions, nested changes are not supported. Attempting to start a change while another change is already in progress will result in an error.
All versions of laravel-changelog with dependencies
illuminate/database Version ^5.1
illuminate/events Version ^5.1
doctrine/dbal Version ^2.5