Issue #38 - Honor PropertyNamingStrategy during serialization

[billcrook]

This is my first pull request, lemme know if I am not following unspoken customs :) Also, let me know if an alternate approach to the issue is desirable.

#38
-Updated CaseClassSerializer to respect the PropertyNamingStrategy if defined
-Added test case

[gmethvin]

I'm not all that familiar with the style conventions of this project, but I would write this as:

private def maybeTranslateName(
    config: SerializationConfig, member: AnnotatedMethod, name: String): String =
  Option(config.getPropertyNamingStrategy)
    .map(_.nameForGetterMethod(config, member, name)).getOrElse(name)

[gmethvin]

Thanks for submitting a fix for my issue. It seems like a reasonable solution to me.

[billcrook]

Oh, I like that much better. I will update it now.

[billcrook]

FYI, I amended the last commit and force pushed.

[gmethvin]

@christophercurrie What would it take to get this merged? This is a feature I'd really like to take advantage of.

[christophercurrie]

Thanks for the patch, and sorry it took me a while to review. I'll get a new build out with this (and some other pending fixes) in the next day or so.