NestJS + TypeORM Tutorial | Repositories, Relations, Migrations & More 

Thanks so much

Sure!

You can use either, but the former provides us with a bit more type safety.

@@mguay Thanks for the response

@@mguayhad the same question, but a follow up how does entityManager work with multiple entities like how does it know entityManager.save(item), entityManager.save(user), feels weird that would be more type safe than using the repository for the respective entity besides that great video learned some cool techniques like the constructor in the entity and creating the abstract entity, just started learning nestjs 2 days been a hardcore express fan for a while

Migration are helpful when you want to seed the db with fresh data for the first time or when you migrate to new DB without losing critical data.. This should be done without the use of API as API are used for single transaction in most of the cases whereas migration will help you inject multiple custom SQL query directly to the db.

That’s next!

@@mguay Wow, amazing, happy to hear that, enjoying the series and love the way you teach. I got chance to learn new aspects of TypeScript which was impossible to find in other places.

How come? That’s a first for me :)

Thank you so much for the support!

@@mguay No problem :) I appreciate the video. I'm dreaming of working with NestJS and after this tutorial my understanding of things just got so much better :)

the best practice is to make a dto an actual class and no doubt about it, otherwise how are you going to document your api using the most popular tool, which is swagger, which literally allows you to pass only class-based types? also, how are you going to validate upcoming request body while interface is not a value and does not exist during runtime? there literally exist npm packages named CLASS-VALIDATOR and CLASS-TRANSFORMER for validating dto schema; but these are only helpers that make your code cleaner, what is actually more important is that you are trying to disrupt dto pattern because there are solid rules behind this principle that should be untouched and unchanged if any concerns, go and check out how it's done in other programming languages, preferably Java because NestJS was strongly inspired by Angular which was strongly inspired by Java but it's just an example, you can go for C#, Python, or whatever else