OpenAPI specification field name capitalisation doesn't match

[CharlieArmstrongDev]

Hey all, anyone got experience with the openAPI specification feature?
I've been trying to hook all the CRUD endpoints into RTK Query, which has it's own code auto-generation that can hook into OpenAPI.

Some awkward result of something in ServiceStack means that while everything in the OpenAPI spec matches the original database fields capitalisation, just like the C# definition of the DTOs. So when I run the code generation, all the types in my typescript frontend match this too.
However, what is actually being sent over the server to the react hooks is an object where the capitalisation has been altered, to be the same as how it'd be in the TypeScript generated DTOs.

Even in the Swagger UI (which comes with the OpenAPI feature) you can see the difference in what it expects and what it gets. Does anyone with some more experience have more of an idea what is happening here? I suppose it's something to do with JSON maybe?

[mythz]

I'd recommend using the TypeScript Add ServiceStack Reference instead which is a feature we have total control over that results in much cleaner code-gen + dev model.

[CharlieArmstrongDev]

Coming back to this just in-case anyone else ever has the same problem - I had missed the option to set this to true: