so i may not call a repository in a controller? would be right: controller -> service -> repo?

I used a Service pattern discussed by Povilas in one of the projects I work on, it was really helpful! Needed to duplicate some functionality on different pages.

Learned that the hard way.

What i personally prefer that in service you have specified methods iwht actual parameters you want to call. So instead of passing request or some general array you just provide like int, strings etc stuff and other arrays, like only what's needed for a method.

The author of the video is fool. This kills the whole point of using the services/usecases. We will not be able to call such service from the API, console application or queue system.

@@anmaner4822 he did a video about not using request on services, so don't call him a fool, cause he did not even say it was good in this video.

​@@thamibn Are you joking? What's the matter what was in the other videos? In this video he uses function auth()->user(). And now the question, what if he calls this service from console? Everything will break, and how i said above this kills the whole point of using services.

@@anmaner4822 he did not use it his not the one who wrote the code, basically in this video he was showing us how services worka or helps with code readability, he was not by any means trying to fix the code inside those services, if you can check there are many wrong things on those services he demonstrated but the video was not about fixing them instead on how to use them Nd how they help. On the other video he clearly thought how to write service classes, and he not to use $request since it won't be accessible when the service is being called on tests,commands etc... I do agree that the service classes used on the video where poorly coded, my point is don't call him fool cause is not his code and he was not fixing them service classes on this video.

I discuss a lot of them in my course: laraveldaily.teachable.com/p/how-to-structure-laravel-project

Not sure if there are "best practices", I guess I would list Laravel Sanctum and Spatie Permissions.

I quite like Jobs, but not for CRUD operations themselves, but rather AFTER CRUD operation. So, like User::create() and then dispatch a Job to send an email.

It's for structure and readability

That would be a full 5-hour course. Maybe someday I will have enough time for it.

Try converting to collection and use unique() laravel.com/docs/8.x/collections#method-unique

@@LaravelDaily thanks you sir, thats working

Yes, valid question, that example code wouldn't work for your scenario.

You could pass the payment method in request and check that payment in service provider and bind the class according to request payment variable.

I have a full separate course: laraveldaily.teachable.com/p/datatables-in-laravel Also, search the channel for "datatables", you will find quite a lot of videos.

It would cost too much. And personally, I don't believe in financial success, as there are already ecommerce platforms on Laravel, but none of them seemed to get traction.

I will have a separate video on Actions, in a few days.

😂😂😂

@@adebajooluwaseyi2124 what's funny?

Done: laraveldaily.teachable.com/p/laravel-for-beginners-your-first-project