You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by k94ll13nn3 October 5, 2023
Hello,
First thanks for this project, it is really useful.
I would like to be able to use the automatic generation of mapping (from the FixMapper method I saw in the repo) when using the Gridify method with custom maps added for some properties.
Using the sample from the documentation, I would like to be able to do this withtout specifiyng Contact.PhoneNumber. If I don't use a custom mapper, the mapping on Contact.PhoneNumber works, but if I use a custom mapper without Contact.PhoneNumber, it does not work anymore (in the sample I could use Contact.Address but my use cases are not as straighforward).
varmapper=newGridifyMapper<Person>().GenerateMappings().AddMap("address",p => p.Contact.Address).AddMap("Contact.PhoneNumber",p => p.Contact.PhoneNumber);// I would like to remove this
Is it possible for now without having to respecify all possible mapping for basic parent.child properties ?
The text was updated successfully, but these errors were encountered:
Discussed in #123
Originally posted by k94ll13nn3 October 5, 2023
Hello,
First thanks for this project, it is really useful.
I would like to be able to use the automatic generation of mapping (from the
FixMapper
method I saw in the repo) when using theGridify
method with custom maps added for some properties.Using the sample from the documentation, I would like to be able to do this withtout specifiyng
Contact.PhoneNumber
. If I don't use a custom mapper, the mapping onContact.PhoneNumber
works, but if I use a custom mapper withoutContact.PhoneNumber
, it does not work anymore (in the sample I could useContact.Address
but my use cases are not as straighforward).Is it possible for now without having to respecify all possible mapping for basic parent.child properties ?
The text was updated successfully, but these errors were encountered: