Thanks a lot for the acknowledgement, @thunderhook!

I will have to take a look at it sometime to learn how it was implemented.

Thank you! Good points. I have rewritten the tests so that the collection also has a different name.
But now the mapping seems to be generated in a different order? At least PresenceUtilsAllPropsWithSource now behaves strangely and sometimes removes the boss. prefix from the path.

I'm not sure how to solve it. I don't quite understand the logic that is implemented with those Deques.
A possible approach is to use a source name that behaves the same (makes the test less readable).
WDYT?

Got it. As suspected, this problem was caused by a reordered mapping method. The PresenceUtilsAllPropsWithSource worked by accident because the nested address mapping happened at the end. The @AfterMapping after method was called by the intermediate method that handled the collection, and therefore went up the path twice.

@filiphr Could you please take another look? Thanks in advance.

Thanks @thunderhook. The changes looked good, I've merged this