Filip Hrisafov

@Obolrom this isn't really high up on the priorities in the moment. If you are interested in contributing feel free to work on it. You can also have a look...

This is not a bug and works as designed. Fluent getters (or component-style getters as written in #3211) are more difficult to implement. >Regular classes with component style getters is...

@mageddo there is a difference between a fluent getter and a record component. In a regular class, how do you determine what should be considered as a fluent getter? Every...

Thanks for raising this @csisy. Just so I understand, why can you use ```java public record Target(String foo, Integer sum) {} @Mapper public interface MyMapper { MyMapper instance = Mappers.getMapper(MyMapper.class);...

@onacit how do you envision the generated mapping code to look like? I believe that it is possible to already achieve what you are looking for using the existing `@Condition`...

I haven't had the time to go through this one yet. Will let you know once I get to it

@thunderhook have you tried this with 1.6.0.Beta2? I think that if you change the `@Condition` to be `@SourceParameterCondition` then it'll work as expected.

Good catch @thunderhook. This is indeed a bug in the way we are rechecking the presence of the source parameters. Shall we rename this issue to tackle that bug?

This is trickier than I thought. The `null` check I believe comes from the `SetterWrapperForCollectionsAndMapsWithNullCheck`. This would work with something like: ```java @Mapper public interface Issue3601Mapper { Issue3601Mapper INSTANCE =...

I actually found a solution for this. Have a look at PR #3620