Is that possible that the mapper can base on the source type to map?

I used AutoMapper (and mediatr which is also developed by Jimmy Bogard) in dotnet core before. It’s pretty nice that see it again in typescript.

However, the code base currently use the destination class to found out the source class is pretty strange.

Thats mean if we have two different source class to project to same vm model will get wrong.

Here is the example that

class User {
  @Expose()
  firstName!: string;
  @Expose()
  lastName!: string;
  @ExposedType(() => Profile)
  profile!: Profile;
}

class User2 {
  @Expose()
  firstName!: string;
  @Expose()
  lastName!: string;
  @ExposedType(() => Profile)
  profile!: Profile;
}

    mapper
      .createMap(User, UserVm)
      .forMember(d => d.first, opts => opts.mapFrom(s => "Khang"))
      .forMember(d => d.last, opts => opts.mapFrom(s => s.lastName))
      .forMember(
        d => d.full,
        opts => opts.mapFrom(s => s.firstName + " " + s.lastName)
      );
    mapper
      .createMap(User2, UserVm)
      .forMember(d => d.first, opts => opts.fromValue("a"))
      .forMember(d => d.last, opts => opts.fromValue("B"))
      .forMember(
        d => d.full,
        opts => opts.mapFrom(s => s.firstName + " " + s.lastName)
      );

Now if we project a User2 obj to UserVm it will still keep using the first mapping

refs: https://codesandbox.io/s/automapper-demo-b3d7p

[nartc]

@vip30 nestjsx-automapper 2.0.7 has been released.

[vip30]

It works as expected and will wait for your release on nestjsx-automapper Thanks you