Use existing mapping rules from an "existing target object" map on a "new instance" map about mapperly HOT 5 CLOSED

Couldn't this be addressed with #513?

from mapperly.

@latonz Yes, that seems like it's the option 2 I described above.

That would do the trick!

from mapperly.

@latonz With getting to know Mapperly a bit better, and seeing that the current behavior is:

1. You define a "main" map eg
   public static partial MyClassDto ToMyClassDto(this MyClass o);
2. You define derivations of the main map and Mapperly will automatically use the rules of the "main" map eg
   public static partial List<MyClassDto> MapToList(this List<MyClass> o);
public static partial IQueryable<MyClassDto> ProjectTo(this IQueryable<MyClass> o);

I'd perhaps suggest that for consistency a ToExistingDto() type mapping should also fall under this same sort of behavior. ie no attribute needed and Mapperly will automatically use the rules of the "main" map.

from mapperly.

When needing a mapping from one type to another Mapperly always uses the default mapping. For your list and queryable examples this will happen as you described as Mapperly needs a mapping from MyClass to MyClassDto down the object tree. However, a ToExistingDto mapping is a new root-level alternative mapping to the default mapping and often the user wants a different configuration for it, therefore I don't think automatically applying the same configuration is a good idea. It would also make the API less explicit and harder to debug.

from mapperly.

Closing in favor of #513.

from mapperly.