Jorge Bodega Fernanz

Hi! Sorry for late response. I think it could be better to detect the seeder by some kind or regexp or maybe by using file name. Feel free to dissent...

I have no problem to use default export, but usually I try to avoid that. [This link](https://blog.neufund.org/why-we-have-banned-default-exports-and-you-should-do-the-same-d51fdc2cf2ad) explain very well why. But what I said, I have no problem with...

Yes, that could work temporary while we still work on this. I will keep this issue open to use it as a reference. Thanks for your help!

For me, the best way to do this is by using non default export and use `instanceof` to check every import as a Seeder, that is an interface. https://github.com/w3tecch/typeorm-seeding/blob/4136b0e0f58a4ec13b17c717bd026043fbdf7ddd/src/types.ts#L23-L28

For me [mikro-orm seeding](https://mikro-orm.io/docs/next/seeding/) is a very good example on how to do this. But is unreleased yet. I'm pretty sure we should create a project and start working on...

Hi! Can you just put some more explicit example, or maybe create a repo to reproduce this? Just because you talked about gender but I cannot see that on entity

I will try to update the message to the last commit ```typescript private async makeEntity(overrideParams: EntityProperty = {}, isSeeding = false): Promise { if (!this.factory) { throw new Error('Could not...

@RaphaelWoude please take a look on this, i will update my PR

I have a fork just to have a functional version of the code, but there are some changes, context is the main one, just because I don't see why it...

Hi! Those changes are okay, but probably some tests are going to fail. In any case, you have to update the branch and add some test to cover that new...