Swagger spec incorrect casing for complex type parameters

[timosnel]

I'm using camel-casing for my route parameters, sometimes I use complex types as parameter which works fine. However, no matter what casing I use for the names of the properties, they are all in lower case in the generated Swagger spec.

In the XML the member looks as follows:

        <member name="NavigationFlagParameters.IncludeChildNodes">
            <summary>
            Indicates whether or not child nodes should be included. 
            </summary>
        </member>

This will be converted into the following in the spec:

{
    "name": "includechildnodes",
    "in": "query",
    "description": "Indicates whether or not child nodes should be included.",
    "required": false,
    "type": "boolean"
},

Am I missing something or is this a bug?

[domaindrivendev]

Yep this looks like a bug. Thanks for reporting it - I'll aim to get a fix out with the next release.

[domaindrivendev]

Should be resolved in latest release - 5.2.0

[mcoolidge]

It seems like all my request parameters are FORCED to camelCase. This looks weird when I have things like DOB or SSN which become sSN and dOB