I am so sorry Jordan I sad before anyone does not tell about service containers , providers , etc... I found you and I am watching your contents and you have contents for them. many many thanks
@Daltoncast11 ай бұрын
Feel free to let me know if there are specific topics you’d like me to cover 😀
@borakayalar11 ай бұрын
Maybe you can tell about dynamic database connection according to user profile.(it is so specific I know that many times we are making CURD apps and that apps so boring :) ) I have a project like that. I can covered it out in one week. coz I am new on laravel. Then I found my problem about it. Middleware sequences were wrong :) logic was when user register to main app than main app create a db for user than user login own admin panel and that panel uses to db of user. it was hard to for me via laravel :) by the way you can take videos about complex project in real life. I dont mean hard codding. The approching or create a application logics@@Daltoncast
@borakayalar11 ай бұрын
meanwhie sorry for my bad english :)
@ricardo.ramirez.r Жыл бұрын
Nice! A side note: the sound is to low
@Daltoncast Жыл бұрын
Thank you. I"ll look into making the audio louder.
@YoKKJoni6 ай бұрын
wayy to low.. unfortunatly because of this i am not watching this video rn.. and prob wornt watch it also..
@antogkou Жыл бұрын
Great video! Pipelines are really becoming a clean code standard for Laravel.
@gabrielodadier2689 Жыл бұрын
Nicely done, i think i will start using pipelines now. Great video
@laravelvuemedia Жыл бұрын
such a nice explanation I love it
@Daltoncast Жыл бұрын
Glad you liked it!
@scotttresor Жыл бұрын
thank for your video and great explanation about pipeline
@collenzaligway4458 Жыл бұрын
Nice tutorial Mate, keep going I really love your videos.
@Daltoncast Жыл бұрын
Thank you so much!
@hassan_codes11 ай бұрын
Thsnk you John, you've shown me thst I know nothing. Gracias 😢
@Daltoncast11 ай бұрын
I’m glad you found value from the content. 😃
@chrispian Жыл бұрын
Great example!! Thanks for sharing.
@Daltoncast Жыл бұрын
Thank you!
@Samuel.Mwangi Жыл бұрын
Happy birthday @Jordan. Subscription earned 🫡
@Daltoncast Жыл бұрын
Thank you, Samuel!
@jeffbee6090 Жыл бұрын
this is great! thanks! love the clean code
@Daltoncast Жыл бұрын
Thanks, Jeff! Glad you enjoyed the content.
@programmertelo28 күн бұрын
thanks for sharing
@Daltoncast28 күн бұрын
@@programmertelo no problem. 😀
@shaungbhone8368 Жыл бұрын
Nice🎉 clean and understand. What a amazing content.
@rahulxcr Жыл бұрын
Thanks that's very helpful.
@KasimSheyi7 ай бұрын
This is really cool.
@everlastingheat75726 ай бұрын
Thanks! Useful information
@arafat124911 ай бұрын
nice one
@gssj-o8p Жыл бұрын
It's a good explanation of how pipelines work in Laravel, they are basically the Chain of Responsability design pattern being applied using Laravel's contract. However this example should be used as an example only since it's totally unecessary to use Pipelines for such situation as building a query. In this case just use ->when() directly without pipes.
@karlson2804 Жыл бұрын
But how about the range data, between or =>,
@DilipKumar-bf4vv Жыл бұрын
Nice explanations. Thanks
@Daltoncast Жыл бұрын
Awesome! I’m glad you found it helpful.
@sashapinchuk54027 ай бұрын
Nice video, but I have a simple question, can we use the __invoke method instead of the handle method in filter classes? Cuz for me is fiilling like the __invoke method more clear.
@sebastianscholz5395 Жыл бұрын
Nice explanation! Why should I use this instead of just applying the "when" to my query builder directly? I think this makes the code harder to read with the pipelines.
@TheMarcelitto6 ай бұрын
Nice!
@ripon594 ай бұрын
well, same thing i achieved with a Trait file with The Builder Pattern process. which is clean too. Why should I use Pipeline especially?
@hasanablak2 ай бұрын
Thank you sir
@Daltoncast2 ай бұрын
@@hasanablak glad I could help 😀
@Daltoncast2 ай бұрын
@@hasanablak glad I could help 😀
@borakayalar11 ай бұрын
great and maybe you dont need to create filter class for each query parameters. Maybe you can parse request query strings and itrate them. Actualy this api is for internal using by developer such as datatables search etc... dev knows already query params. And I think you can manage with one filter class. Meanwhile it is a nice content many thanks.
@Daltoncast11 ай бұрын
Thank you
@YusnielBrocard Жыл бұрын
Nice example
@Daltoncast Жыл бұрын
Thank you
@Khader-1 Жыл бұрын
Great by all means! keep it going, Subscription earned
@vhpm18 Жыл бұрын
Excelent
@AtiqurRahman-n2i Жыл бұрын
Nice. Go ahead. The sound can be better.
@Daltoncast Жыл бұрын
Thank you. I'll look into making the audio louder.
@mariano.pualiu Жыл бұрын
I've always found pipelines processing fascinating, but I wonder how could I bifurcate the pipeline into 2 or more processes under some conditionals correctly, so far I've though to create new processing pipelines with in a pipeline accordingly to some respective conditionals
@creative2brains882 Жыл бұрын
That is great clean code
@creative2brains882 Жыл бұрын
you can do this class UserFilters { public function __construct(protected Request $request) { } public function handle(Builder $builder, Closure $next) { return $next($builder) ->when($this->request->has('name'), fn ($query) => $query->where('name', 'REGEXP', $this->request->name)) ->when($this->request->has('email'), fn ($query) => $query->where('email', 'REGEXP', $this->request->email)) ->when($this->request->has('bod'), fn ($query) => $query->where('bod', 'REGEXP', $this->request->bod)); } }
@manishdeshpandeАй бұрын
Lousy audio. Unable to comprehend what's being said.
@unnikrishnanadoor3 ай бұрын
can't hear anything very little sound
@sudhirdhawle53707 ай бұрын
NO sound
@ikarolaborda726 Жыл бұрын
My rule number one: NEVER use model methods in controllers. Controllers shouldn’t even know the models exist. Either use services or action classes, and of course, repository (believe it or not, there were times when i had to avoid using eloquent) But, excellent example anyway. You’ve used cpp and other stuff most PHP devs don’t even know of
@hassan_codes11 ай бұрын
Service classes are my go-to. I too avoid using Eloquent when dealing with "complex" queries. I started doing that after learning how Eloquent parses and builds it queries