Case-insensitive deserialize and camelCase serialize options about jil

[kevin-montrose]

I'm really reluctant to add additional options to Jil, as each new option has to be accounted for in the typecache classes.

Jil already supports customizable names (via [DataMember] and [JilDirective]), which is hopefully sufficient for most cases. If not, then a more extensible JSON library (such as JSON.NET) would be a better choice for a project.

[mexx]

Maybe the camelCase option could be provided as assembly wide attribute.
I have many classes currently serialized with camelCase, it would be simpler to add an attribute to the assembly as to edit all the properties on all classes.
Just a thought.

[phillip-haydon]

This is a shame, I just came across this project, but lack of camelCasing is silly.

[jchannon]

I think case sensitivity is quite a big deal, most json libs support this feature.

[AlienEngineer]

+1 for this feature

[liyongjing]

+1 for this feature

[hallvar]

+1 for this feature

[NickCraver]

+1 for this from me too. It'd eliminate a ton of code where this is used. Rather than an ever-increasing n attributes (as well as the need for plugin assemblies to have dependencies in a CoreCLR world), a Jil option controlling serialization globally would be much more optimal.

[razbensimon]

+1

[Wazner]

For anyone reading this issue and hasn't looked at the pull requests yet.
There currently is a pull request that implements camelCasing.

See #154