Closed mlegenovic closed 8 months ago
You are right, this is a regression. We migrated row reading into an intermediate type so that applications no longer need to consume uni-directional types. However, the migration isn't complete. We now use RowDocument
to store all information instead of Row
. We need to reinstate the Row
-based approach.
Long-term, the mismatch between converters (Reading Row -> Entity
, Writing Entity -> OutboundRow
) will be resolved into Entity <-> RowDocument
.
Until then, we have to fix this regression. Thanks for letting us know.
According to the documentation (Overriding Mapping with Explicit Converters) it should be possible to create custom mapper with a Row2Entity converter.
This worked quite well until version 3.2.0. As of this version, all Row ->Entity converters are ignored.
Is this a bug, or intentional, just the documentation not adapted?