OpenAPITools/openapi-generator

[GO][Server] Question: Life after generation

Open

#3547 opened on Aug 2, 2019

View on GitHub
 (7 comments) (4 reactions) (0 assignees)Java (26,243 stars) (7,516 forks)batch import
Enhancement: FeatureHacktoberfestServer: Gohelp wanted

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

Tech stack
go
Domain
backend
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
OpenAPI Generator usageGo programmingServer stub generation
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the current recommended workflow for Go server generation by reviewing the project documentation (e.g., README, docs/ folder) and any linked discussions in this issue. The user suggests gin swagger integration; evaluate whether such a feature exists or is planned. Check if there are any related PRs or comments from maintainers regarding post generation customization.