OpenAPITools / OpenAPITools/openapi-generator
[REQ] typescript-axios modelPropertyNaming
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
Is your feature request related to a problem? Please describe.
Compared to typescript and typescript-node, typescript-axios is the only one without modelPropertyNaming. We were switching away from typescript-node because request has been deprecated and wanted to use typescript-axios but it would have been a huge breaking change to lose camelCase modelPropertyNaming.
Describe the solution you'd like
typescript-axios should include ObjectSerializer and camelCase modelPropertyNaming to support users migrating from typescript-node.
Describe alternatives you've considered
I am currently using typescript but that has its own problems and I basically had to replace httpApi with my own implementation based on axios.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the typescript-axios and typescript-node generator implementations, then locate where ObjectSerializer and modelPropertyNaming are defined or configured. Check how the existing typescript generator handles camelCase naming and validate generated client output against that behavior. Done means typescript-axios supports ObjectSerializer and camelCase modelPropertyNaming for migrations from typescript-node.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100