11.0
Closed Jan 31, 2024
100% complete
Version 11 sees a complete rebuild and re-imagining of the library and will not be backwards compatible.
Changes include:
- Moving away from the DB facade and using Eloquent methods and relationships to update aggregate fields. This provides developers a lot more functionality and power by allowing them to alter how aggregate relationships are used.
- Simpli…
Version 11 sees a complete rebuild and re-imagining of the library and will not be backwards compatible.
Changes include:
- Moving away from the DB facade and using Eloquent methods and relationships to update aggregate fields. This provides developers a lot more functionality and power by allowing them to alter how aggregate relationships are used.
- Simplified configurations. Point your config at the relationship, and customise anything beyond defaults. That's it.
- Models must now implement a class and use the provided trait. This provides inherent validation in the objects being passed around.
- More behaviours - including averages.
- Ability to have chained behaviours. For example, you could have a count cache updating a field on an aggregate table, which then triggers a sumcache update on a separate aggregate table.
- Better documentation.
- Easy database logging support
This milestone is closed.
No open issues remain. View closed issues or see open milestones in this repository.