Skip to content

Conversation

JMolenkamp
Copy link

@JMolenkamp JMolenkamp commented Feb 28, 2025

Alternative to #777, less impactful, keeps InvokerModel intact.
Try combining parts if no property or field was found for a single part to allow for mapping properties that contain periods.

From #777:

The InvokerModel stores the property path as a period joined string. When building the expression for a property path, this string is split on the periods, which makes it impossible to have a property name that contains periods.

Obviously, this is kinda obscure, but I actually ran into this issue. It is possible to have a property name with a period when dynamically building types where pretty much all naming restrictions go out of the window.

@JMolenkamp JMolenkamp force-pushed the feat-map-members-containing-periods branch from 8af487a to 07c9763 Compare March 4, 2025 20:00
@JMolenkamp JMolenkamp force-pushed the feat-map-members-containing-periods branch from 07c9763 to d8f7693 Compare March 4, 2025 20:03
@DocSvartz DocSvartz merged commit 3a92a3d into MapsterMapper:development Sep 30, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants