swagger-api / swagger-api/swagger-codegen
[GO] Server, no docs and empty responses
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
Go server does not have /docs and does not return responses. I'm sure you are aware of this, but it's not clear to a developer which features are supported on each server. Maybe you need a feature grid?
Swagger-codegen version
Swagger declaration file content or url
default PetStore example
Command line used for generation
none
Steps to reproduce
Go to: https://editor.swagger.io
Using the PetStore example, then click:
- Generate -> nodejs-server
- Generate -> go-server
Then run each server and go to:
http://localhost:8080/docs
http://localhost:8080/v2/store/inventory
Notice how NodeJS version returns a response, but Go server version does not.
Related issues/PRs
none
Suggest a fix/enhancement
First create a feature grid, to show which servers support which features. Second add the features when possible :)
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 generating the PetStore example as a go-server from editor.swagger.io and compare its /docs and /v2/store/inventory behavior with the nodejs-server. Define the supported-server feature grid, then verify which missing documentation and response behaviors are expected to be addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100