-
-
Notifications
You must be signed in to change notification settings - Fork 93
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
Support for property name amendment #336
Comments
@moltar Thank you for using this! That can convert type name to use the |
Thank you for replying so quickly! I saw that type renames are possible via library. But my use case is to rename the property names, not types. E.g. Interface foo { To Interface foo { Sent with GitHawk |
Oh sorry, I'm mistaken. But in a normal case, we use it for converting the API response or request definition to TypeScript definition. Do you want it in any situation? |
It is not a problem that it will not match, because I will convert the responses too to match camelCase. |
Did you consider to align naming convention between API producer & consumer? |
Off-topic:
I am curious how is this usually done, especially when API producer and consumer are written in different languages that following different casing convention. Do you still try to set a casing convention between API producer and consumer? In our situation producer (our API server) is written in ruby (which uses Most of our consumer will do a |
It is now possible to convert property names using the plugin's post process. |
It'd be great to be able to filter the property names and rename them too.
Our API returns
snake_case
property names, but JS/TS world is mostly operating incamelCase
.I'd like to be able to convert these before output.
Thanks.
The text was updated successfully, but these errors were encountered: