Skip to content
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

Flexible name matching #57

Merged
merged 10 commits into from
Mar 17, 2016
Merged

Conversation

chaowlert
Copy link
Collaborator

Fix #49

Pls merge #56 before reviewing this issue.

This PR allows match property names with different convention. Usage is

TypeAdapterConfig.GlobalSettings.Default.NameMatchingStrategy(NameMatchingStrategy.Flexible);

or

TypeAdapterConfig<Foo, Bar>.NewConfig().NameMatchingStrategy(NameMatchingStrategy.Flexible);

By defining as flexible, it will allow to match between PascalCase, camelCase, lower_case, and UPPER_CASE. This feature is applied to both property mapping & class flattening. And users can defined their own convention (ie, prefix, suffix, replace) by create new NameMatchingStrategy.

@chaowlert
Copy link
Collaborator Author

@BuzzDee3000 Could you kindly test this feature whether it is what you want or not?

@BuzzDee3000
Copy link

@chaowlert I will check this asap.

eswann added a commit that referenced this pull request Mar 17, 2016
@eswann eswann merged commit ea684ac into MapsterMapper:master Mar 17, 2016
@chaowlert chaowlert mentioned this pull request Mar 22, 2016
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.

Ignore Case-sensitivity on Propertynames
3 participants