swagger-api / swagger-api/swagger-codegen
online api should support modelPropertyNaming
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
Swagger-codegen version
Swagger declaration file content or url
Command line used for generation
curl -X POST https://generator3.swagger.io/api/generate -H "content-type: application/json" -d '{
"specURL": "https://petstore.swagger.io/v2/swagger.json",
"lang": "typescript-angular",
"options": {
"additionalProperties": {
"modelPropertyNaming": "original"
}
},
"type": "CLIENT",
"codegenVersion": "V3"
}' -o generated-files.zip
Steps to reproduce
Related issues/PRs
Suggest a fix/enhancement
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
Start by reproducing the curl request against https://generator3.swagger.io/api/generate with the typescript-angular language and modelPropertyNaming set to original. Trace how the online API handles the options object, then verify that the generated archive reflects the requested property naming.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100