Видео

Great ❤

answer for this: Illuminate\Contracts\Container\BindingResolutionException Target [Illuminate\Database\Eloquent\Model] is not instantiable while building [App\Http\Controllers\BlogPostController, 00000000000000560000000000000000, App\Repositories\Repositories\BlogPostRepository]. ??

nice work

Isn't it over complicated

Great lesson! Thanks a lot!

Dzień dobry mate! I just discovered you! Keep up the good work! Subscribed!

Good tutorial. This was cool. What's with the folder structure? Wonder why he didn't talk about why there's a src folder there.

Does this code handles databse execption or any other execption rather than custom execption?

Why TF you decreased the pitch soo much ? these annoying youtubers, never gonna learn

Awesome

thank you bro. penjelasannya bagus

this is probably why the JS ecosystem always better, the vercel AI SDK is just to good to not use.

Laravel uses "messages" objects with builder pattern not DTOs but that is detail ofc :) Thanks for video

extremely like. always as usually constantly %)

When I listen to your fluent English, it sounds like you're being electrocuted or sitting on a . Tnnx for explanantion

wow

So instead of having a simple controller method that only interacts with a FormRequest and a Model, you've now added complexity with a superfluous Service class and a DTO. It may look cool, but using such a basic examples to try and demonstrate their usefulness is a mistake. public function store(StoreBlogPostRequest $request) { $blogPost = BlogPost::create($request->validated() + ['source' => BlogPostSource::App]); return new JsonResponse(BlogPostResource::make($blogPost), Response::HTTP_CREATED); } public function update(UpdateBlogPostRequest $request, BlogPost $blogPost) { $blogPost->update($request->validated()); return new JsonResponse(BlogPostResource::make($blogPost->fresh()), Response::HTTP_OK); } What should have taken 2-4 lines in 2 methods contained in 1 class became 6 methods inside 3 classes. There is a case to be made for Service classes and DTOs, but this is not one of them.

Holy f I was trying to build my own

how is it different from repository pattern?

Thnx for approach guide. But could you not speed up the words partially within eat the volume at the end of phrase.. 😅

You have great videos in laravel. keep this up

I think controller and service layer is enough for most of the laravel applications. Hence we are re creating all the method in the repository which is already available in the laravel eloquent model, it seems like a repetitive work without any additional benefit. We can just keep our controller clean and pass the business login to service class , then resolve the function my accessing database via eloquent models and then return the result to controller. in that way we can use the laravel already build eloquent powers easily and quickly.

Thank you very much!

We wanted you Przemysław Przyłucki ? ?How are you ? why you dony push video ? push video about you , channel please!!!!

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

thanks for the great video

i have never worked with any php framework before. Its funny to see that back when i started learning php i designed a request handler that seems pretty similar to this piece of laravel.

I would add the transformation method to request classes. In my opinion you should not have to extend DTO classes when adding new pieces of code eg. API v2 instead you should have a method called asDto(or toDto) in the request class and call them instead of making X static factory methods. Overall great content :)

Great tips, but i more like to use different actions as class, not as a part of service. Its easy to extend from basic model to others

Any tips for getting this to work with Vue 3?

This is awesome, i hope you deep dive on DDD on the next episodes

Good Video!

Man you would love C# haha. Thanks for the video!

Use handle() method instead, not the __invoke().

Hey! How do you approach having different validation rules in the store and update actions? For example, a StoreBlogRequest which marks all fields as required, VS an UpdateBlogRequest which doesn't (for example, you just wanna update the name). Would you create more than one DTO and mark the properties as nullable?

Hopefully if you're going to be making upstream requests on every page load (or every user login) the developer will be making sure to perform reasonable caching. Since this is Laravel it should be pretty configurable, but something to be conscientious of. Also, presumably the upstream service (e.g. growthbook, in this case) is utilizing standard HTTP cache headers that Guzzle can respect and cache centrally using the configured middleware (e.g. memcached if you're on a cluster or something).

Yikes. Model mutators and observers will be enough guys. But if you want to Over-engineer your code, then go on with dto or something like repository pattern. 😅

Really good man! I would like to know what you think about adding an extra layer: the repository. Because thats kinda whats going on my in job rn, laravel + service pattern + dto + repository, I feel like the Model itself could act as the Repository, what do you think?

Awesome video series. what laravel version is this ?

17:20 - Shouldn't our DTO have a method like toArray so that we can manually avoid passing all the parameters? I mean, they correspond to the properties of the model. Or is this a bad practice? Like this public function toArray(): array { $properties = get_object_vars($this); $array = []; foreach ($properties as $key => $value) { $snakeCaseKey = Str::snake($key); $array[$snakeCaseKey] = $value; } return $array; } and then BlogPost::create($dto->toArray());

5:50 - what about duplication in BlogPostRequest validation for api and app? Can we get rid of it?

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.

I think we should use RepositoryContract interfaces instead of Repository classes in the constructors of Handler classes.

We miss you

Mordo, if you use AWS there is a native way to integrate it though Event Bridge - almost no code solution and you don't pay for lambda invoke. Trust me mordziu I am an engineer. But well explained, thumb up