Jorge Bodega Fernanz

The most painful part of upgrading TypeORM is the connection refactor, that is true, and I really don't like how the Seeder actually work, like a tree, so I'm really...

My idea for the next version is just to remove the tree and run all the seeders in order, letting the users to choose the order with `01-Seeder` or `01Seeder`...

No plans to work on this since I can work on this but cannot deploy. If you can wait until someone came back to work or give me access, it's...

I don't have permissions to add secrets to github, so I cannot add the deploy system I've worked on my fork, and I won't do it manually. So until I...

Hi! Can you share how are you running the seeder? Just running `nest build` somehow? Could be useful, I cannot reproduce this. BTW, I updated your issue to use markdown,...

Please @alfaben12, could you check what @harveysanders said? If that fixes your problem, I could try to do something with path validation (Maybe print files loaded with verbose flag?)

I'll check this with sample code, maybe docs could be updated with this info.

I'm looking on `resolveEntity` method, for me its quite unclear and could be better, probably related on the behaviour of: ```typescript user.labelingTickets = Array( factory(LabelingTicket)().createMany(quantity) as any, ); ``` Let...

Hi! I've been testing this and I cannot reproduce the problem. I you checkout `117-javascript-heap-out-of-memory`, I've modified the sample to approach your problem, please try if you can or add...

Hi! Sorry for late response. Seems like a problem with typeorm and how naming works. Did you try same query in some other places?