Download the PHP package imanghafoori/eloquent-history without Composer
On this page you can find all versions of the php package imanghafoori/eloquent-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 eloquent-history
Eloquent History Tracker
It keeps track of your table rows and just like git, it only records changes for each update you make.
Installation:
Usage:
Note: As an alternative to registering the Hisotry Tracker inside service providers, you can simply use the WithHistoryTracker trait inside your desired model(s):
Note Since this works based on eloquent model events, if you update your rows without firing events the changes would not be recorded.
This includes performing an update query without fetching the row first.
So as an example:
Public API:
Note: all the queries are done within the transaction to guarantee that you do not end up with inconsistent data.
The most important method is the getHistoryOf which accepts an eloquent object, an array of columns to be fetched and an array of columns to be counted as a change.
$importantCols: What it means?!
Consider a situation when you have a table with 10 columns and there are 2 forms to edit column values.
For example, a form to edit first name, last name, bio and etc, and another form to only change password.
Ok, now you need to show the submission history of the first form.
Here you have to exclude the password column otherwise the submissions of other forms will appear in the history of the first form.
Here we don't want to show bio on the table but we want to show other metadata about that, for example, the date and the username.
:raising_hand: Contributing
If you find an issue or have a better way to do something, feel free to open an issue or a pull request.
:exclamation: Security
If you discover any security-related issues, please use the security tab instead of using the issue tracker.
:star: Your Stars Make Us Do More :star:
As always if you found this package useful and you want to encourage us to maintain and work on it. Just press the star button to declare your willingness.
More from the author:
Laravel Microscope
:gem: It automatically find bugs in your laravel app
Laravel HeyMan
:gem: It allows to write expressive code to authorize, validate and authenticate.
I speak to everyone in the same way, whether he is the garbage man or the president of the university. "Albert Einstein"
