Openapi-generator: [GO][Server] Question: Life after generation

[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?

[wing328]

@boskiv I think you're referring to the generation gap pattern and we totally welcome such enhancement.

Ref: https://github.com/OpenAPITools/openapi-generator/issues/426

May I know if you've time to make the contribution? I can show you some good starting points.

[boskiv]

@boskiv I think you're referring to the generation gap pattern and we totally welcome such enhancement.

Ref: #426

May I know if you've time to make the contribution? I can show you some good starting points.

Sure, with pleasure. What I have to do?

[boskiv]

Have found https://github.com/golang-standards/project-layout
Should we follow it as generation result?

[wing328]

Have found https://github.com/golang-standards/project-layout

That looks good to follow

cc @antihax (2017/11) @bvwells (2017/12) @grokify (2018/07) @kemokemo (2018/09) @bkabrda (2019/07)

[wing328]

Please PM me via Slack so that I can show you where to start: https://join.slack.com/t/openapi-generator/shared_invite/enQtNzAyNDMyOTU0OTE1LTY5ZDBiNDI5NzI5ZjQ1Y2E5OWVjMjZkYzY1ZGM2MWQ4YWFjMzcyNDY5MGI4NjQxNDBiMTlmZTc5NjY2ZTQ5MGM