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
What I would do to avoid duplication is to have only one Mapper instance for all the mappings, as Mapper is thread-safe and there shouldn't be conflicting cases.
In your .injectMapper(mapper1, ConfigProfile.class), what is ConfigProfile.class for ?
If that means "I want the ConfigProfile class to be mapped only by mapper1, then what about that :
I need to inject an existing mapper into another mapper to avoid duplication mapping rules.
For example, if want to inject an existing mapper to manage the ConfigProfile class mapping, I expect something like
The text was updated successfully, but these errors were encountered: