swagger-api / swagger-api/swagger-codegen
[Swift4] openapi tag should be used instead of swagger
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
I've recently started using swagger codegen. This is proving to be very helpful! :-)
swagger specs for v 3.0.0 state that the first tag used in the swagger document should be "openapi" but the swagger codegen requires this to be "swagger". This makes it a little bit of a hassle when moving between swagger editor and codegen
https://editor.swagger.io
Swagger-codegen version
2.2.3
Swagger declaration file content or url
Command line used for generation
na
Steps to reproduce
na
Related issues/PRs
na
Suggest a fix/enhancement
can this be standardised easily?
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 source file, test, or reproduction command is identified. Start by comparing the OpenAPI 3.0 document produced by Swagger Editor with swagger-codegen 2.2.3, then locate the parser or validation entry point handling the top-level tag. Done means codegen accepts the standard "openapi" tag and coverage verifies generation from such a document.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi, swift
- Domain
- api, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100