melzar / onion-architecture-boilerplate Goto Github PK

Hi @Melzar, first: Your boilerplate is helping me a lot since it's my first deep dive in all those great architectural techniques.

I'm reading hgraca's article while reading your code

I was going down trough the stack and found this method:

It is creating an AddEquipmentRequest to pass as parameter, but in the method definition:

It is expecting CreateEquipmentRequest.

I know that both classes have the same signature:

So, is EquipmentRepository class defining the wrong signature for addEquipment method or am i missing something?

Thank you!

Hello.

I quite like your repo. Suppose, in a given Service function, you wanted to make changes to multiple repositories within a transaction. How would you handle that while still abstracting away TypeORM?

Thank you.