Observed behavior
When creating or updating records via Forest Admin’s Laravel integration, I’ve observed that Eloquent model events (such as creating, created, updating, updated) are not being fired. This behavior was identified after implementing custom logic within these model events which did not execute as expected during create/update operations initiated from Forest Admin’s UI.
Expected behavior
I expect that when records are created or updated through Forest Admin, all relevant Eloquent model events should be triggered.
Upon further investigation, it appears that Forest Admin’s integration utilizes the Laravel Query Builder for direct database operations, specifically through methods like insertGetId($data) for creating records, which bypasses the Eloquent model layer. This approach prevents Eloquent model events from being triggered. In my situation, I have some field values which need to be generated at create time (whether created via Forest or via my Laravel app).
Context
- Project name: CNProject
- Team name: Operations
- Environment name: Development
- Agent (forest package) name & version: forestadmin/laravel-forestadmin:3.0.1
- Database type: postgres
- Recent changes made on your end if any: none
.