Replies: 2 comments 6 replies
-
When you are using In any case in 1.6 (also part of 1.6.0.Beta1) there is Will something like this work for you? |
Beta Was this translation helpful? Give feedback.
6 replies
-
Thanks to all of you. I think my mistake was that I focused on type compatibility. But for MapStruct the name of the property is the main focus. So thank you very much for MapStruct |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
If I write a mapper with component model
SPRING
, which uses other mappers, like this:the used mapper
ReferenceMapper
is injected via field or constructor injection. This works fine for production code.But in tests, it would be great to have also a setter for every used mapper, so that I can setup a test as unit test outside of a Spring context. Currently I have to annotate with
@SpringBootTest
, even if I don't need the Spring context.So, would it be possible to generate setters for each used mapper? IMHO it would ease writing simple and fast tests.
Beta Was this translation helpful? Give feedback.
All reactions