swagger-api / swagger-api/swagger-codegen
I have exactly the same issue as described above.
Open
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
I have exactly the same issue as described above.
errorOnUnknownEnum=true
breaks compilation because parameter is named input, but in the exception is concatenated (wrongly) as text...
Any idea for work around or when it's going to be fixed?
Originally posted by @avachos in https://github.com/swagger-api/swagger-codegen/issues/10356#issuecomment-1039868854
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 file or test is named. Start by locating the generated exception handling for errorOnUnknownEnum and compare the parameter names input and text; done means the generated code compiles without the reported mismatch.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100