Martin Adámek

Well, we will break it with a breaking release, that's fine. We could as well state that this is an experimental API subject to change. Either way, we need to...

I also believe this is about behaving the same as the platform/API, and we surely want this to behave the same as the apify client.

Better to open this on slack, i am not opposed to changing this, but it would be great to first understand why it was like that (and I doubt anyone...

I already tried to do this and failed, it's far away from simple 🙃 Planning to have another look later, but I would greatly appreciate some help on this one....

Yes, but what should that method be for? The ORM won't use it anyhow. Also, you keep saying DTO, but what does it mean, raw DB results or something else?...

Sidenote: I don't like the idea of `helper()` supporting the class handle like this, its purpose is to provide a wrapped entity instance for a given entity instance, not entity...

> My bad... I thought the difference between wrap() and helper() was exactly that helper() takes in a type class, while wrap() takes in an entity instance, so that seemed...

PR welcome. > The only way You can use metadata hooks to do this dynamically. https://mikro-orm.io/docs/configuration#onmetadata-hook Also I don't understand how would you even end up in this situation, if...

Those are two different things, yes, `cascade` option is used to infer defaults for `update/deleteRule`, but they operate on the opposite sides, and `cascade` is app level configuration that requires...

> the cascade behavior, that is set by default to [PERSIST] when not overridden Cascade persist has nothing to do with `update/deleteRule` option.