swagger-api / swagger-api/swagger-codegen
Feature request - http/2 support in generated clients and servers
Open
Nobody has claimed this yet.
Enhancement: Feature
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
This ticket is about keeping track of effort to implement http/2 based clients and servers.
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 files, tests, or entry points are named. Start by identifying which generated clients and servers are in scope and how HTTP/2 support should be defined; the issue is only tracking effort, so the completion criteria cannot be determined from this ticket alone.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100