swagger-api / swagger-api/swagger-codegen
Improments: Revision of code generation of okhttp-gson
Open
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
In context of : "library" set to "okhttp-gson".
- so removal of unsed fields
- so removal of possible unsed imports
- so removal of unsed class
- upgrade to Java 8 / or even option for Java 11+:
- so using lambdas
- so using missing diamond operator
- try-catch-resource construction
- using "var"
- less own code rather using Java classes
- make hidden classes, methods ... by access modifier to avoid using "internal logic"
- option to not generate "@Schema" and even imports for that
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
The issue names the okhttp-gson library and generated Java output but no repository files or tests. Start by locating the okhttp-gson generation entry point and its templates, then define the supported Java versions and scope of each requested cleanup. Done requires the requested generation options and output changes to be specified and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100