OpenAPITools / OpenAPITools/openapi-generator
[REQ] Better Structure for Go Server Project
Open
Nobody has claimed this yet.
Enhancement: Feature
Server: Go
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
Is your feature request related to a problem? Please describe.
Hi,
Now the go-server creates a project like this
│ main.go
│ Dockerfile
│ .openapi-generator-ignore
│
├───go
│ model_user.go
│ api_default.go
│ routers.go
│ logger.go
│ README.md
│
├───api
│ openapi.yaml
│
└───.openapi-generator
VERSION
Describe the solution you'd like
Shall we create a structure similar to the go-swagger generates folders.
cmd/<server's name>/main.go
models/<all models>
Thanks !
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 reviewing the current Go server output, including main.go, the go/ directory, api/openapi.yaml, and the .openapi-generator metadata, then compare the requested cmd/<server's name>/main.go and models/ layout with go-swagger's structure. Done means the generated project has an agreed, documented folder organization and its generated files remain usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100