As for me, packge is just logical, I somehow hate the package that working with my database, it's feel like I can not control it.
If my package have to communicate with the database, I prefer to defining a PackageTableInterface and working with it. Then in my application logic, I will do an implementation for that interface.
Btw, it's just my practice
, not best practice
.
I would have liked an answer to this too as i am in the same situation
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community