We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I am using Gin to create an API that has one endpoint accepting a map as a querystring. This is described here:
https://github.com/gin-gonic/gin#map-as-querystring-or-postform-parameters
A map encoded in a query string (named map) looks like:
map
/endpoint?map[key1]=value1&map[key2]=value2
This concept seems to match what swagger specification refers to as "deep objects" (see https://swagger.io/docs/specification/describing-parameters/ and https://swagger.io/docs/specification/serialization/).
I believe swaggo does not support this yet. Is that correct? If so, are there any plans to add support for it?
The text was updated successfully, but these errors were encountered:
All the links are for OpenAPI 3.0, swagger is OpenAPI 2.0 compliant.
Sorry, something went wrong.
Indeed. Closing this ticket in favor of #386
No branches or pull requests
I am using Gin to create an API that has one endpoint accepting a map as a querystring. This is described here:
https://github.com/gin-gonic/gin#map-as-querystring-or-postform-parameters
A map encoded in a query string (named
map
) looks like:/endpoint?map[key1]=value1&map[key2]=value2
This concept seems to match what swagger specification refers to as "deep objects" (see https://swagger.io/docs/specification/describing-parameters/ and https://swagger.io/docs/specification/serialization/).
I believe swaggo does not support this yet. Is that correct? If so, are there any plans to add support for it?
The text was updated successfully, but these errors were encountered: