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
You may remember the issue I opened a while ago about dynamically changing mappings. That is now supported in 5.0. Still, in my approach, I define an 'OverrideMapper' (implementation can be seen here). That solution works, yet is somewhat clunky. And I had to put it into LinqToLdap because it accesses various internal properties.
Do you see a better approach to have that additional mapper outside the LinqToLdap lib? Ideally I'd go back to using the mainline but that means an approach where I can override the mapping in the "this property goes there" style. This mapping actually gets configured in a GUI, then it is injected with an instance of OverrideMapper at runtime.
The text was updated successfully, but these errors were encountered:
You may remember the issue I opened a while ago about dynamically changing mappings. That is now supported in 5.0. Still, in my approach, I define an 'OverrideMapper' (implementation can be seen here). That solution works, yet is somewhat clunky. And I had to put it into LinqToLdap because it accesses various internal properties.
Do you see a better approach to have that additional mapper outside the LinqToLdap lib? Ideally I'd go back to using the mainline but that means an approach where I can override the mapping in the "this property goes there" style. This mapping actually gets configured in a GUI, then it is injected with an instance of OverrideMapper at runtime.
The text was updated successfully, but these errors were encountered: