Refactor enum, type, and property names #3
Description
In general, most of the data structures and types were generated using NSwag directly against the Chaster API JSON definitions. This has the benefit of being much faster in getting a working code base, but often the generated names are not very intuitive.
New names would be a huge improvement and I think it would assist in documentation efforts, but at the same time I suspect most people will be using a layer of abstraction above ChasterSharp to manage the service.
This is an important issue for me, but in the real-world it's less consequential.
(This probably makes more sense as a project, rather than an issue)