Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: Camelise component parameters and handle snake->camel on incoming data and camel->snake on outgoing data #213

Open
MbBrainz opened this issue Dec 15, 2023 · 0 comments

Comments

@MbBrainz
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant