kiqstyle / eloquent-versionable
Versioning behaviour for eloquent models
Installs: 14 446
Dependents: 0
Suggesters: 0
Security: 0
Stars: 0
Watchers: 1
Forks: 2
Open Issues: 5
Requires
- php: ^8.2
- illuminate/database: ^9.0|^10.0|^11.0
Requires (Dev)
- nunomaduro/phpinsights: ^2.11
- orchestra/testbench: ^7.0
- phpmd/phpmd: ^2.15
- phpunit/phpunit: ^9.3.3|^10.0
- squizlabs/php_codesniffer: *
- dev-master
- v1.5.0
- v1.4.0
- v1.3.3
- v1.3.2
- v1.3.1
- v1.3.0
- v1.2.0
- v1.1.2
- v1.1.1
- v1.1.0
- v1.0.4
- v1.0.3
- v1.0.2
- v1.0.1
- v1.0.0
- dev-trying-using-new-versioned-at-column-instead-of-updated-at
- dev-dependabot/composer/guzzlehttp/psr7-2.5.0
- dev-dependabot/composer/symfony/http-kernel-5.4.20
- dev-fix-bug-on-old-version
This package is auto-updated.
Last update: 2025-08-09 20:50:17 UTC
README
Careful: Eloquent first method on versioned models will get the first result that doesn't has next value, meaning if you update the first register it will set a date to next column and it will find the next register with next column with value null, that could be another id
For contributors
- INIT
- RUN: 'make up'
- RUN: 'make composer-install'
- TESTS
- RUN: 'make test'