Stefan Parker

Actually https://ent.dev/docs/custom-graphql/gql-input-object-type, https://ent.dev/docs/custom-graphql/gql-interface-type, and https://ent.dev/docs/custom-graphql/gql-union-type also make the same reference.

Nuts.

Ok, hear me out, I've thought about this some more and I have some ideas on how to make patterns even better. So, instead of converting to `type`, leave it...

I say leave `ISomePattern` as an interface, because if you're worried about backwards compatibility, you don't need to change the name to `ISomePatternBase` and then extend that in the other...

It'll still be a mixin, but you'll be able to add custom fields/methods to the mixin. https://gist.github.com/Swahvay/bc91257bdd89371e5b77bf12c7359705

Yeah, I realized there's no need to use the special overriding instance name hack here. You can simply name the original instance `ISomePatternBase` and have `ISomePattern implements ISomePatternBase`. That should...

And it'll still be backwards compatible.

Also, the base interface should `implement Ent` too.

You are missing a couple things. For one, you need to change the `Constructor` type to be `type Constructor = new (...args: any[]) => T;`. Then you need to move...

I guess you also need to update implementations: ```js export class BarnInfoBase extends LocationMixin(class {} as (new (...args: any[]) => Ent)) implements Ent, ILocation { ... } ``` (You could...