forked from loafle/openapi-generator-original
* Update go-gin-server templates to return a configurable library Before this change, the user would be required to make changes in the generated code. This makes it really hard to update the API and the documentation at the same time. With this change, the generated code can be imported as is and used. The user just needs to set the handler functions for each endpoint. * Use spaces instead of tabs for api files * Use space instead of tab for ApiHandleFunctions in go-gin-server * Update samples for go-gin-server
Go API Server for petstoreserver
This is a sample server Petstore server. For this sample, you can use the api key special-key
to test the authorization filters.
Overview
This server was generated by the [openapi-generator] (https://openapi-generator.tech) project. By using the OpenAPI-Spec from a remote server, you can easily generate a server stub.
To see how to make this your own, look here:
- API version: 1.0.0
Running the server
To run the server, follow these simple steps:
go run main.go
To run the server in a docker container
docker build --network=host -t petstoreserver .
Once the image is built, just run
docker run --rm -it petstoreserver
Known Issue
Endpoints sharing a common path may result in issues. For example, /v2/pet/findByTags
and /v2/pet/:petId
will result in an issue with the Gin framework. For more information about this known limitation, please refer to gin-gonic/gin#388 for more information.
A workaround is to manually update the path and handler. Please refer to gin-gonic/gin/issues/205#issuecomment-296155497 for more information.