| Code with Dary | |
| Laravel Fundamentals | April 29, 2021 |
| Laravel 8 Autentication & Mailing | May 5, 2021 |
| Laravel 8 API Course | April 17, 2021 |
| Coder's Tape | |
| Jobs, Queues & Events 2021 | February 21, 2021 |
| Test Driven Laravel | June 30, 2019 |
| New in Laravel 7 | March 2, 2020 |
| Laravel Collections Guide | March 3, 2019 |
| Laravel Package Development | February 21, 2019 |
| Laravel 6 Advanced | November 24, 2019 |
| Laravel 6 Beginner | January 4, 2020 |
| Laravel 5.8 - From The Ground Up | August 21, 2019 |
Note: Dates are subject to change (being outdated).
Note 1: It can be beneficial to format with Resources for more flexibility.
Note 2: You can avoid mixing transformers into repositories by using an external transformer.
Note 3: The repository should only be used to retrieve the data. It's a common mistake that some programmers use repositories for storing, updating, or deleting, but it’s not meant to be like that. If you need to store, update, or delete then you have to have a persistent layer.
Additional Reference: stackoverflow.com/questions/57340681/should-we-save-update-models-in-repository-pattern