swagger-api / swagger-api/swagger-codegen
Parameter of "similar name" leads to wrong code generation of fields
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Tested in context of : "library" set to "okhttp-gson".
If 3rd party API returns for some strange reason e.g.:
{
"text" : "text",
"Text": "text"
}
Client generated based on specification file with fields:
private String text;
private String text;
But this is wrong as it should either add automatically postfix or take respect e.g. to schema "title" to generate field name in generated model class.
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
No source file or test is named. Reproduce the issue using the specification file and the okhttp-gson library, then inspect the generated model for the text and Text fields; done means both API fields produce distinct valid field names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100