Modeling Inheritance in Redwood+Prisma

Hi all,

Is there a preferred way to model inheritance in Redwood+Prisma? From what I found, prisma is lacking deeper support for this. The solution I was thinking of is along the lines of what’s described here:

Apologies if this has been discussed here before - I didn’t find anything. I’d be happy to get a link to previous discussions if I missed something.

Update: We’ve been using the model described in the basedash link and it’s creating a lot of boilerplate for field conversion etc in the sdl/service layer. While it should technically still work, it’s making us question whether this is the right approach. Would love to get some feedback from the community around this.