OpenAPITools / OpenAPITools/openapi-generator
[GO][Server] Question: Life after generation
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
What is the recommended flow after generation server?
Should I change code under ./go folder?
Or I need to override Api methods in my own files?
Would the interface generation, in this case, be a better solution?
I guess that maybe one of the ways is the implementation of logic in a particular file and adding a file to the .openapi-generator-ignore, but how in this case will the update occur if the specification YAML changes?
I have tried https://github.com/mikkeloscar/gin-swagger before. I'd like this approach.
Should we try to implement it here?
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 reading the issue's questions about the ./go folder, generated API methods, interface generation, and .openapi-generator-ignore. Compare the requested gin-swagger-style flow with how the OpenAPI YAML specification drives regeneration. Done would require a decided, documented approach or an agreed implementation scope, but the issue does not identify files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, openapi
- Domain
- backend-api-design, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100