Add Mapster support for object mappings about dotnet-webapi-starter-kit

[ittyabrehman]

@iammukeshm Sure, i will add and raise the PR soon

[cetindogu]

This library is popular, nowadays

[iammukeshm]

Could you implement the same and raise a PR?

[dsoltesz]

How is this different than automapper

…

________________________________ From: itttyab Rehman ***@***.***> Sent: Tuesday, September 21, 2021 5:41:26 AM To: fullstackhero/dotnet-webapi-boilerplate ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [fullstackhero/dotnet-webapi-boilerplate] Add Mapster support for object mappings (#64) @iammukeshm<https://github.com/iammukeshm> Sure, i will add and raise the PR soon — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#64 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AALFFSJPDYJRKRFUYHHSZW3UDBHMNANCNFSM5ENK2OPA>.

[ittyabrehman]

@dsoltesz First of all thank you for asking the question. The real advantage of using Mapster is its performance and efficient memory usage. It is almost 2.5 times faster than AutoMapper. And twice as fast as the other known mapper's frameworks. In addition to this Mapster automatically generate the dtos which save a lot of time when working on a big codebase

You can see the results of a test run below

Source: screenshot taken from Mapster official repository:

[iammukeshm]

Let's skip the part where mapster creates it's own DTOs..Let's have our DTOs...we will just use Mapster for mapping the object, and replace Automappr implementation..Is that ok? @ittyabrehman

[ittyabrehman]

instead of replacing automapper i think we should declare a property in appSettings which will represent either to use automapper or mapster for mapping objects. what you say @iammukeshm

[iammukeshm]

Yes, we can do as the second step though...i will create an abstraction over the mapping later.

[ittyabrehman]

#66 Added and merged Successfully