I may be misreading the OpenAPI spec, but I believe the following to be true:
According to the Openapi 3 spec, an in:query parameter that has:
style = form
explode = true
schema = some object
=> This should result in a query string spec build from the properties of the schema object.
The explorer treats this as a text blob input instead of making parameters from each property. There are other "style" values that I believe allow for a blob entry but form + explode should be treated differently (also form + not-explode).
So, for example, this schema should yield an endpoint that looks like .../some_path?var1=some_value&var2=123 (notice the name "params" does not appear):
However, instead of rendering the individual properties as query parameters, the explorer shows this:
Note also that style=form and explode=true appear to be the defaults when not specified explicitly.
There are multiple other values for "style" and a table of combinations of style + explode and what that is supposed to mean for the query string formatting. I won't pretend to understand them all. but I would like to see if we can at least support the "form" style.
I may be misreading the OpenAPI spec, but I believe the following to be true:
According to the Openapi 3 spec, an
in:query
parameter that has:=> This should result in a query string spec build from the properties of the schema object.
The explorer treats this as a text blob input instead of making parameters from each property. There are other "style" values that I believe allow for a blob entry but
form
+explode
should be treated differently (also form + not-explode).There is a large matrix of possibilities for these two fields). See: https://swagger.io/specification/#style-examples
So, for example, this schema should yield an endpoint that looks like
.../some_path?var1=some_value&var2=123
(notice the name "params" does not appear):This should also work for $ref schemas such as:
However, instead of rendering the individual properties as query parameters, the explorer shows this:
Note also that
style=form
andexplode=true
appear to be the defaults when not specified explicitly.There are multiple other values for "style" and a table of combinations of style + explode and what that is supposed to mean for the query string formatting. I won't pretend to understand them all. but I would like to see if we can at least support the "form" style.