You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In using the typescript-axios generator, I found that the default behaviour of using positional paramters for query parameters to be dangerous, as described in #6288 - and so I'm using useSingleRequestParameter=true. This then exposes the paramName (which is normalised to camelCase) to my application. I need the parameter names in original form as described by the openApi spec.
Describe the solution you'd like
An option to change the renaming behaviour of paramName, which works in the same way as enumPropertyNaming or modelPropertyNaming parameters.
Describe alternatives you've considered
Changing the naming in the client application to use the more JS-idiomatic camelCase names.
Changing the api to use camelCase names.
Disabling useSingleRequestParameter - this is the least work but I think it's too dangerous.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In using the typescript-axios generator, I found that the default behaviour of using positional paramters for query parameters to be dangerous, as described in #6288 - and so I'm using
useSingleRequestParameter=true
. This then exposes theparamName
(which is normalised to camelCase) to my application. I need the parameter names in original form as described by the openApi spec.Describe the solution you'd like
An option to change the renaming behaviour of
paramName
, which works in the same way asenumPropertyNaming
ormodelPropertyNaming
parameters.Describe alternatives you've considered
Changing the naming in the client application to use the more JS-idiomatic camelCase names.
Changing the api to use camelCase names.
Disabling
useSingleRequestParameter
- this is the least work but I think it's too dangerous.The text was updated successfully, but these errors were encountered: