swagger-api / swagger-api/swagger-codegen
Capture spec version in client
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
It would be beneficial if there was a way to make sure a generated client is restricted to a server version.
Even if there is no restriction, I would like a way to capture the version of the spec that the client was generated against.
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 locating the generated-client flow and how the OpenAPI specification is represented during generation; clarify whether the goal is only to record the spec version or also enforce server-version compatibility. Done means the intended version behavior is defined and covered for generated clients.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100