[Feature Request]: Camelise component parameters and handle snake->camel on incoming data and camel->snake on outgoing data
MbBrainz opened this issue · comments
According to the Google Typescript style guide, we should use lowerCamelCase for parameters.
Currently, because the openAPI standard is with snake case the current codegen generates types with snake_case parameters. This makes sense, because you wouldnt need a conversion step here, however it would be nice to have the option to generate lowerCamelCase parameter names.
personal context: Im working on a library where they are already using lowerCamelCase and manually performing all the conversions, but they still manually update that library when the api changes. This is imo a waste of engineering time, but they cant just drop the CamelCase, cause there are many users of their library already.