Laravel + Service Pattern + DTOs = ❤️❤️❤️ 

yeah

I couldn't agree any better

Thanks Natan! If you sprinkle some DDD on top it gets even better 🤓

Thanks Lucas!

Thanks for watching!

Hi Adriano! Thanks for the kind words. Lemme explain the reasoning: The biggest reason why DTOs are useful is it unifies the data passage through your application. Let's say you have a piece of business logic that needs to be executed from your app, public api, command and a job. DTOs ensure that proper data gets passed to the service. Also, if you ever add a property, it will cause errors in places where it was not implemented / handled which also prevents bugs

So using the Model itself as a DTO would be the same, right? or how in typescript to use an interface

@@felipeflashmaster using the Model as a DTO itself would clutter the Model into a mess, if you're planning to implement DRY, that would not be a recommended approach.

You're welcome!

Yeah I use both of them in my workflow! Def worth checking out for anybody interested though!

Thanks! Glad you enjoyed it and good luck on your project

While refatoring, I wonder how you would handle Request for update that has fields set as sometimes for validation. Considering for patch request, not all fields will be supplied.

@@codewithtee Often times I just duplicate the request, I like this approach because it's the most flexible one. You could try and extract common rules but as the resource gets more complex I think it just adds unnecessary complexity in something that should be sime. Another solution is to simply check the method in the request and modify the rules array but I find it harder to read :)

same here too..

Legend!

Which you can still do by instantiating the DTO from the constructor. Imo array passing loses all of the benefits of type checking built into the class

Thanks so much! Types as in strings, ints etc? What would you like to know about them?

@@saaslaravel everything hehe, like using a separated file, best practices, how to use it in a function like boot(): void and all that stuff.

It really depends on what you are looking for from the solution. I'd say - if you don't have a good reason to introduce a repository - don't do it. If you want to have more fine grained control over your persistence layer (i.e to handle CQRS more easily) go for repository!

Thank you! It's called Catpuccino Mocha

I don't have it unfortunately but will probably start doing it going forward

And you dont need to use Dto u can just do create($request) //already validated clean data

Thanks Artem! It really depends on the scenario, I think there is a use-case for both Option A: Nested models created all at once. Example: You create BlogPost and it has different "sections" of content, or you create a Recipe that has Ingredients Solution: In this example you'd have a RecipeDTO that has all of the recipe properties, and either an array of IngrednetDTO, or a IngredientDtoCollection (the latter if you want something that's more type-safe) Option B: Creating a new model and associating it with existing ones Example: You select which users should have access to a project Solution: In this example you'd have a ProjectDTO, that'd contain an array with IDs of users to associate and then simply attach it to a pivot table Lemme know if this makes sense!

@@saaslaravel Thank you for your help.

That's true, but I prefer using constructor. The method tends to have 2/3/4 arguments - with type hints it takes a lot of space, and when it lives on constructor level I can just define it once :D

@@saaslaravel makes sense as well :) I tend to use actions in method binding and if I use a service in more than one method I would promote it to the constructor.

Hey there! It depends on the situation, generally speaking with updates I'd not go with nulls because partial updates are pretty sexy - if you use spatie/laravel-data - they handle it out of the box with Optional type hint

The main benefit is making sure that the data you're passing is valid data that service can consume. This is especially useful when you have multiple pieces of app - console, public api and internal api calling the same service. You can just start implementing it on new services and then gradually go over existing code! Hope that helps :)

@@saaslaravel Obrigado !

Además que simplifica el constructor

It really depends on the usecase so it's hard to give you a good response here but you can also nest them and utilize arrays with phpdoc type hinting to skip some of the type limitations of php

Yes, it's just a concept that you need to know from scratch. Just a regular, plan, old PHP class. Nothing wrong with using the package!

You can include all data into one dto or pass two separate DTOs. It will depend on the usecase

I prefer to be explicit when possible, realistically, just use spatie/laravel-data which handles this out of the box

Until your app had 1200 endpoints and some places haven't been touched for years - yeah

@@saaslaravel yeah? But I prefer laravel's defaults for easier maintenance and debugging. Also KISS. Pfft

Idk, why is it bud?

million times better and understandable than any indian out there that i cannot understand