The best "advanced" laravel vids on youtube right now! I've been building laravel projects for 5 years and I still learn something from every video you upload, thanks for the great content
Never thought that filters may be implemented in such a nice pattern. I always made filtering through hard sql queries in repository. Keep going, your videos are the best laravel content on youtube!
Plz explain why you are using such complex things pipelines, ___invoke function, Just if condition for fillter , and if it is too mush code put it in traits
I didn’t know about pipeline but i think laravel provides the "when()" method on query builder instances. It’s simple and "eloquent" (pun intended 😂 ) i think but you probably already know about it. Your post seems to be for demonstrating the pipeline tool, thanks.
Damn, I have loved how this guy thinks through, punctures and re-evaluates his decision and progress, a sure skills problem-solving mental processes, "THANKS"
Can this be implemented with repository pattern? to have for example in EmojiRepository in the function getFilterableEmojis() can we move here the logic with the pipeline to return just $filterable->builder->get() and in the controller to have like return EmojiResource::collection( $emojiRepository->getFilterableEmojis($request) );
So the request itself is not passed to the DTO but to the static function that bootstraps the object. The DTO itself doesn't have a request property or access to it, it's just a helper that bootstraps the class from it that I like to use for convenience as they are usually tied to each other more or less. So often times I'd just have a bunch of these i.e. fromArray, fromRequest, fromCollection etc.
Like with a lot of other stuff in Laravel There was no need to reinvent the Chain Of Responsibility pattern and slap the name Pipeline on it. Any developer(java, php, C#) worth their salt knows about the chain of responsibility pattern, I don’t think the same can be said about this Pipeline thingy. I’m not even going to go into the world of complexity that is the query building example. That being said, thanks for putting the effort of making this video, I learned something new and I appreciate it.
I mean you are right - this is CoR, but Laravel called it differently. My purpose here is to show the tools available in the framework. The thing is that depending on your usecase a tool can be good or bad. When defining a super complex query that has a bunch of filters, this abstraction works pretty great for me.
issue with the code. at 2:42 message said "Naughty boy" but what if the user is a girl or worse a LGbTV++ or something 😉. PS: it's just a joke and Your code is good thanks for vid.
Наука
The best "advanced" laravel vids on youtube right now! I've been building laravel projects for 5 years and I still learn something from every video you upload, thanks for the great content
Comments like that make my day! Thank you so much and glad it was valuable
This is awesome. Big up.
Awesome
Use handle() method instead, not the __invoke().
Holy f I was trying to build my own
Never thought that filters may be implemented in such a nice pattern. I always made filtering through hard sql queries in repository. Keep going, your videos are the best laravel content on youtube!
IMO the filters example is a bit over-engineered but the Onboard is superb! by the way I used these often...great video
Plz explain why you are using such complex things pipelines, ___invoke function,
Just if condition for fillter , and if it is too mush code put it in traits
nice
I didn’t know about pipeline but i think laravel provides the "when()" method on query builder instances.
It’s simple and "eloquent" (pun intended 😂 ) i think but you probably already know about it.
Your post seems to be for demonstrating the pipeline tool, thanks.
Ey, I love your videos, can you kindly make a video specifically for roles, and tag me on it. 😊
Hi Trevor! I already have two videos on permissions & roles, you may want to check them out
Damn, I have loved how this guy thinks through, punctures and re-evaluates his decision and progress, a sure skills problem-solving mental processes, "THANKS"
Can this be implemented with repository pattern? to have for example in EmojiRepository in the function getFilterableEmojis() can we move here the logic with the pipeline to return just $filterable->builder->get() and in the controller to have like return EmojiResource::collection(
$emojiRepository->getFilterableEmojis($request)
);
👍
Very good video and channel! I'm thinking to use this to refactor our registration process
Nice pattern, I will maybe try it out ;)
its awesome, it also looks like criteria in l5 repository package
13:30 is passing the whole $request to DTO recommended practice? I've known that representation layer should not be aware of the request object.
So the request itself is not passed to the DTO but to the static function that bootstraps the object. The DTO itself doesn't have a request property or access to it, it's just a helper that bootstraps the class from it that I like to use for convenience as they are usually tied to each other more or less. So often times I'd just have a bunch of these i.e. fromArray, fromRequest, fromCollection etc.
Loving the VSCode setup (looks like VSCode?).
What’s you’re setup?
It's actually PhpStorm with Catpuccin theme
Great show. And waiting for more :)
Very nice vid, thanks
Like with a lot of other stuff in Laravel
There was no need to reinvent the Chain Of Responsibility pattern and slap the name Pipeline on it.
Any developer(java, php, C#) worth their salt knows about the chain of responsibility pattern, I don’t think the same can be said about this Pipeline thingy.
I’m not even going to go into the world of complexity that is the query building example.
That being said, thanks for putting the effort of making this video, I learned something new and I appreciate it.
I mean you are right - this is CoR, but Laravel called it differently. My purpose here is to show the tools available in the framework.
The thing is that depending on your usecase a tool can be good or bad. When defining a super complex query that has a bunch of filters, this abstraction works pretty great for me.
issue with the code. at 2:42 message said "Naughty boy" but what if the user is a girl or worse a LGbTV++ or something 😉. PS: it's just a joke and Your code is good thanks for vid.