AutoMapper VS mapperly

AutoMapper

The 13.0 Upgrade Guide page was created back in April, but there is no sign of the release yet.

The most well-know is probably AutoMapper, but it's not universally liked.

AutoMapper - well for automapping

When working with AutoMapper, we often bump into runtime errors due to invalid mapping configuration, such as this one:

What problems will resolve automapper?

If you are a fan of data mappers, you might want to enhance the implementation with additional extension methods. Here is an example for AutoMapper.

I'm wondering myself. Most mappers like https://automapper.org/ will make a best effort mapper automatically via introspection. If this is just a DSL/annotation suite that requires explicit, complete mapping implementations then this strikes me as a re-implementation of parts of kotlin in kotlin.

Check out https://github.com/riok/mapperly

There are alternatives doing this already e.g. https://github.com/riok/mapperly

No sure if I understand your problem correctly, but maybe something like Mapster or Mapperly could help with that, given that it can generate source code instead of using reflection or expression trees.

That's why I'd suggest Mapperly. It outperforms Automapper too, Chapsas made a video about that recently.

Do note that AutoMapper is reflection based. If you'd like a compile time mapper, looking into something like mapperly or MappingGenerator