Martin Adámek
Martin Adámek
No, its not, you get a different error that is not related to this issue.
Hmm the other issue is the assignability in general, as this fails too: ```ts const a: FindOptions = {} as FindOptions; ``` Looking into that.
Yeah we can add another conditional to the type explicitly for `any` and resolve the populate type to just `string[]`, maybe we could make it work with just `FindOptions` too...
Btw while this is indeed something to debug more, I believe for your original issue you could get around this by not using `FindOptions` in generics - you could have...
Gave it few more hours but I am affraid this is either impossible to solve with current implementation, or simply above my skills. Will leave this open for few days,...
Will close this, gave it another try after the TS 4.8 refactor, but no luck, sounds like a won't fix to me. One other workaround that you could use is...
Can you try just released 5.0.2? There were some fixes in schema support.
I can't reproduce this. Here is a passing test case: ```ts import { PrimaryKey, Entity, Property, ManyToOne, MikroORM, wrap } from '@mikro-orm/core'; @Entity({ schema: '*' }) export class Company {...
Oh so you want to have relations between wildcard schema entities, now I get it. What is the use case? This sounds quite weird and is indeed not supported. You...
> If there could be a way to insert/specify two schemas in query that would solve the issue and would make it so it would work with N schemas related...