Confusing casing recommendation in style guide

[robcresswell]

openapi-typescript version

7.9.1

Node.js version

24.6.0

OS + version

macOS 15.6.1

Description

Hello! First off, thanks so much for this collection of libraries, I use them all the time and they're great. Also, I've filled in the required fields, though they have nothing to do with the bug report.

I was very confused by the casing recommendation (https://openapi-ts.dev/advanced#embrace-snake-case-in-js) in the docs. Is OpenAPI supposed to be snake cased? I couldn't find any casing recommendations in the spec, and I couldn't really understand what recommendation the docs were supposed to be making.

Reproduction

https://openapi-ts.dev/advanced#embrace-snake-case-in-js

Expected result

I suppose I would expect no opinions on casing, because its nothing to do with the spec, to my knowledge?

Required

• My OpenAPI schema is valid and passes the Redocly validator (npx @redocly/cli@latest lint)

Extra

• I’m willing to open a PR (see CONTRIBUTING.md)

[evermake]

@robcresswell, I guess this section of the docs does not promote any specific casing nor it argues that snake_case is recommended in OpenAPI; it just says that though camelCase is preferred in JS, it is recommended to avoid renaming names of parameters/methods/etc. in the input OpenAPI spec (which often doesn't match the JS styleguide) and better to preserve original names.

[robcresswell]

I sort of understand, I think. It feels a little unnecessary to me, but its unimportant.