User implemented mapping methods ignored when return type is string? about mapperly

[latonz]

Thanks for creating this issue. The documentation of Mapperly in those areas (matching and priority of mappings) definitely needs some improvements (I created #196 to track this).
As the original matter of this issue seems to be resolved, I'll close this for now.

[mshgh]

Disregard my comment, please. I have realized

• none of my custom mapping methods were actually used.
  The generated implementation was identical to the one I provided. Lesson learned - I don't need custom method in case target class has constructor accepting source type. Pretty cool!

  private EntityId StringToEntityId(string id) => new EntityId(id); // not needed!

• the custom mapping methods cannot be static
  It's a bit of surprise as mapper class can be static, but not a big deal. Fixed

note: I have realized as well the type match takes into consideration nullability, I guess this is intentional
this method is used (according to my classes definition)

private string? EntityIdToString(EntityId? id) => id?.Value;

but this one is ignored and .ToString() is used instead

private string EntityIdToString(EntityId id) => id.Value;