swagger-api / swagger-api/swagger-codegen
Add okhttp4-gson codegen to support OkHttp 4.12.0
Open
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
In current okhttp4-gson codegen is using OkHttp 4.10.0 which has cve .Is there any workaround to use OkHttp 4.12.0
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-3635
Swagger-codegen version
Swagger declaration file content or url
Command line used for generation
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 locating the okhttp4-gson codegen templates and the dependency declaration that pins OkHttp 4.10.0. Check the related generation tests, if available, and verify that generated clients build with OkHttp 4.12.0. Done means okhttp4-gson supports the newer version without breaking generated clients.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100