<a href="https://jotonsutradhar.com/blogs/5/details" target="_blank" rel="noopener nofollow">https://jotonsutradhar.com/blogs/5/details</a>

Laravel Kids

The post provides a detailed guide on how to implement CRUD (Create, Read, Update, Delete) operations in Laravel using the repository pattern, which helps in organizing code better and making the application more maintainable.

Laravel CRUD with Repository Pattern

Why? Missing some very powerful tools Laravel offers in FormRequests, and I never understood the need for another abstraction layer between what Laravel offers with the ORM.
If you say its for making it easier to switch databases, mock data for testing, and implement caching. But laravel offers tools to do all of that that works with the ORM/Models etc.
Just busy-work for minimal upside in my opinion.

I believe the cover image needs an edit 😅
Aside from that, it’s a good and clear article

<a href="https://app.daily.dev/ripon52" data-mention-id="DOvtgPexBKRr796d2DMpn" data-mention-username="ripon52">@ripon52</a> Thanks for sharing🤠

Damn, as if that thumbnail typo was made to increase comments. Nice one 💪🏻

Don’t need the service provider. I believe if your repository extends the interface and you pass that interface Laravel will know.