You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
It looks like at the moment AllowNullPropertyAssignment is only accepted at Global (mapper level). Thus multiple mapper classes need to be created if AllowNullPropertyAssignment is only required for one mapping method.
Describe the solution you'd like
If possible a MapperAllowNullPropertyAssignment attribute can be introduced to allow adding this attribute at method level. This approach is similar to other configuration such as RequiredMappingStrategy.
Is your feature request related to a problem? Please describe.
It looks like at the moment
AllowNullPropertyAssignment
is only accepted at Global (mapper level). Thus multiple mapper classes need to be created ifAllowNullPropertyAssignment
is only required for one mapping method.Describe the solution you'd like
If possible a
MapperAllowNullPropertyAssignment
attribute can be introduced to allow adding this attribute at method level. This approach is similar to other configuration such asRequiredMappingStrategy
.Additional context
If there are technical challenges to achieve this, the current solution of implementing multiple classes is still good enough.
The text was updated successfully, but these errors were encountered: