Andreas Ravnestad
Andreas Ravnestad
No feedback, assuming this is solved. Please let me know if this is still an issue with the latest version.
As mentioned above this is basically a limitation in Mapster that can be worked around. PR's are still welcome if someone finds a nice solution that is compatible with code...
@satano Sorry for the late reply. Unfortunately we can't support this scenario due to code generation limitations. Glad you figured it out :)
Hi @moghimi, may I ask which version of Mapster you are using?
@moghimi I am struggling to understand the problem here. Did you actually mean to do: ```csharp destination = source.Adapt(destination); ``` and not: ```csharp destination = source.Adapt(); ``` Because the latter...
No, but your code isn't doing what you think it does. You are overwriting `destination` with a completely new POCO object mapped from `source`. Please use `destination = source.Adapt(destination);` if...
Fixed in #590
@ventii Yes this is a known issue, the name matching strategy does not seem to be working as intended.
See also #388.
@Geestarraw Do you happen to be using ASP.NET Core in this case?