Skip to content

Property names can now also be configured in code on ConnectionSettings #1062

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Nov 19, 2014

Conversation

Mpdreamz
Copy link
Member

This PR allows you to configure property names in code on ConnectionSettings globally using expressions.

i.e

.MapPropertyNamesFor<MyCustomClass>(props => props
    .Add(p=>p.MyProperty, "mahPropertah")
)

…e argument exception that describes which mapping is not allowed
@Mpdreamz Mpdreamz removed the WIP label Nov 19, 2014
@gmarz
Copy link
Contributor

gmarz commented Nov 19, 2014

LGTM 👍

gmarz added a commit that referenced this pull request Nov 19, 2014
…ping-in-code

Property names can now also be configured in code on ConnectionSettings
@gmarz gmarz merged commit dd94fc6 into develop Nov 19, 2014
@gmarz gmarz deleted the feature/property-name-mapping-in-code branch November 19, 2014 20:45
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.

3 participants