Using automapper with Prisma

[t0xa]

Hello @nartc,

First of all, thank you for such incredible project. It helped me to build things much faster. Do you have a Patreon or Buy me a coffee so we can show our appreciation?

Could you please help me to understand how to correctly use Automapper with Prisma ORM.

The main problem is that Prisma generates type instead of class. For example:

export type Endpoint = {
  id: number
  guid: string
  description: string | null
  url: string
  status: EndpointStatus
  createdat: Date
  updatedat: Date
}

Is there a way of doing mapper.createMap() with types or some other way of creating such mapper?

Thank you in advance.

[nartc]

hi @t0xa, thanks for the kind words. I don't have Pateron or Buy me a coffee which I think I should set up (I do have Github Sponsors but people tend to stay away from Monthly fee 😛). Thanks again for your support.

As far as mapping with types/interfaces, there's @automapper/pojos but I am not too confident about it. If you could, please check out the POJOs plugin out and see if it works for you, what can be improved, what needs to be fixed etc... I'll gladly support and provide fixes.

[t0xa]

Hi @nartc, thanks a lot for suggestion. Let's close this question for now. I will open another ticket in case of issues.

May I suggest to enable Github Discussion feature so that such questions would be easier to navigate.

Regarding the sponsoring, can you do something similar to what OctoPrint does on her main page?

[nartc]

I have just turned on Discussions. And I'll check out that OctoPrint. Thanks!

[notmedia]

I just tested Prisma types with pojos plugin and it works perfect.

[t0xa]

Thanks @notmedia. Out of curiosity, did you have any Prisma.JsonValue fields in your schema?

[notmedia]

Yes, in my case I have entity with JsonValue. The structure of JSON field depends on another field
So, I created class for this Json and then with automapper create an instance of that class for json field.

I need this for GraphQL, for automatic resolve type

// This type generated by Prisma
type PrismaEntity = {
  type: 'one' | 'two';
  config: JsonValue,
}

@ObjectType()
class OneConfig {
  constructor(config: { [K in keyof OneConfig]: OneConfig[K] }) {
    this.test = config.test;
  }

  @Field({
    description: 'Test value',
  })
  test: string;
}

@ObjectType()
class TwoConfig {
 ...
}

const ConfigUnion = createUnionType({
  name: 'ConfigUnion',
  types: () => [OneConfig, TwoConfig],
});


@ObjectType()
class Entity {
  @Field(...)
  type: 'one' | 'two';
  
  @Field(...)
  config: typeof ConfigUnion;
}

// Created for POJOs mapping from Prisma entity to backend entity
createMetadataMap<Entity>('Entity', {
  type: String,
});

createMetadataMap<PrismaEntity>('PrismaEntity', 'Entity', {
  type: String,
});


@Injectable()
class PrismaEntityProfile extends AutomapperProfile {
  constructor(@InjectMapper('pojos') mapper: Mapper) {
    super(mapper);
  }

  mapProfile() {
    return (mapper: Mapper) => {
      mapper.createMap<PrismaEntity, Entity>('PrismaEntity', 'Entity').forMember(
        (destination) => destination.config,
        mapFrom((source) => {
           switch(source.type) {
             case 'one': return new OneConfig(source.config as OneConfig)
             ...
           }
        })
      );
    };
  }
}

[nartc]

Converted to a discussion for ease of conversation. cc @t0xa @notmedia

[linjer]

@notmedia Thanks for providing an example!

Have you figured out how to handle Prisma's include types? It appears to come back as something like PrismaEntity & { relatedObj1: Obj1 }

[notmedia]

@notmedia Thanks for providing an example!

Have you figured out how to handle Prisma's include types? It appears to come back as something like PrismaEntity & { relatedObj1: Obj1 }

@linjer
Hey! I moved from Prisma to another ORM. The main reason is prisma’s autogen that placing types inside node_module which we can’t modify, use decorators or provide logic.
Prisma advantages sounds great but broke normal architecture patterns. So I cant remember how to handle it, sorry. This was a long time ago