swagger-api / swagger-api/swagger-codegen
Fix, improve CLI arguments handling and improve help, diagnostic messages
Open
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
- multiple occurrences of array options (-D, --instantiation-types, --type-mappings, --additional-properties, --import-mappings, --reserved-words-mappings) are not supported although documented. The last occurrence is used.
- zero command exit status in case of error.
Swagger-codegen version
3.0.26-SNAPSHOT
Swagger declaration file content or url
any
Command line used for generation
Steps to reproduce
$ swagger-codegen-cli generate
$ swagger-codegen-cli config-help
$ swagger-codegen-cli generate -l java
Related issues/PRs
#11005 .
Suggest a fix/enhancement
I will submit a PR. It is #11005 .
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 with the swagger-codegen-cli generate and config-help entry points and reproduce the listed commands, including repeated array options and invalid invocations. Compare the observed help, diagnostics, and exit statuses with the documented behavior; the issue identifies PR #11005 as the submitted fix, so confirm that work before starting.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100