Комментарии:
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
Ответить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.
ОтветитьNice tutorial Mate, keep going I really love your videos.
ОтветитьI am sorry but the sound/volume is too low
Ответить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
ОтветитьNice explanations. Thanks
Ответитьthis is great! thanks! love the clean code
ОтветитьNicely done, i think i will start using pipelines now. Great video
Ответить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
ОтветитьNice🎉 clean and understand. What a amazing content.
Ответитьthank for your video and great explanation about pipeline
Ответить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.
Thank you for the video. I'm learning Laravel API and this video is great. But what about filters like gt, lt, equal, etc.?
ОтветитьExcelent
ОтветитьThat is great clean code
ОтветитьGreat video! Pipelines are really becoming a clean code standard for Laravel.
ОтветитьHappy birthday @Jordan. Subscription earned 🫡
ОтветитьGreat example!! Thanks for sharing.
ОтветитьNice. Go ahead.
The sound can be better.
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.
But how about the range data, between or =>, <= for instance?
ОтветитьNice!
A side note: the sound is to low
Thanks that's very helpful.
Ответитьsuch a nice explanation I love it
Ответить