Stefan Parker

I think your error was also stemming from this: https://github.com/lolopinto/ent/compare/fix-1739?expand=1#diff-f1be87cfb1d9e732f22b07d00c5f336294cccf0f5f09f94866b742efc003f5d3R23 should be `return class FeedbackBaseMixin extends BaseClass implements IFeedbackBase {`

You're right. You need to make one more subtle change. Each file needs to have its `type Constructor` definition point to the base interface. `type Constructor = new (...args: any[])...

I'm confused a little bit because I'm not getting any errors in my patterns with edges. What is the problem you're seeing?

I believe so. I've even started using it already. I think maybe a v0.3 feature might be to be able to add GraphQL fields to the pattern, but that would...

It would also be nice if these patterned ents implemented interfaces in graphQL schemas, so that I could just do ```graphql ... on MyPattern { someField } ```

A case I have that would be great to be covered: **Ents:** - Horse - HorseInfo (holds gender enum - foreignKey reference on horseID) - HorseBreedingInfo (holds damID and sireID...

It's my understanding that pagination works by using the where clause as a sort of starting point in an ordered list. So, the basic example of `ORDER BY id`, to...

The should probably be generated as: ```js addField('horseIDs', input.horseIds); if (input.horseIds) { input.horseIds.forEach((horseId) => this.orchestrator.addInboundEdge( horseId, EdgeType.HorseToCompetitionEntries, NodeType.Horse, ), ); } if (this.existingEnt && this.existingEnt.horseIds) { this.existingEnt.horseIds.forEach((horseId) => { if...

This is a new field. I ended up going a different direction anyways, so I'm not blocked on this, but it's still a valid bug.

Everything else seemed to work except that builder setting edges.