naming conflicts when using the CamelCasePropertyNamesContractResolver

[drpeck]

Taking Organisation as an example, there is an Address properties and an Addresses properties with [JsonProperty("address")] attached.

If your app use the CamelCasePropertyNamesContractResolveras the ContractResolver then Address and Addresses are both given the name "address" and you get an exception thrown. It would be better if [JsonIgnore] were applied to Address. This is probably not the only issue where this conflict exists.

[mortenbock]

This library should specify it's own contract resolver, and not rely on whatever was specified in the default settings:

new JsonSerializerSettings
{
    NullValueHandling = NullValueHandling.Ignore,
    ContractResolver = new DefaultContractResolver()
}