Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • O openapi-generator
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3,476
    • Issues 3,476
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 402
    • Merge requests 402
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OpenAPI Tools
  • openapi-generator
  • Issues
  • #3547
Closed
Open
Issue created Aug 02, 2019 by Administrator@rootContributor

[GO][Server] Question: Life after generation

Created by: boskiv

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?

Assignee
Assign to
Time tracking