You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The parameters are expanded just fine if there is only one possible request object. But if you have more than one "type" of request that can be formulated, and you express this with a oneOf, the parameters are no longer expanded / exploded. The whole object is simply serialized as the value of the named parameter. Even if there is only a single object inside the oneOf the exploding still gets messed up.
I thought it might of had to do with the Request Snippets, but it still happened when they were disabled, and I was able to pinpoint the issue to the use of oneOf.
Q&A (please complete the following information)
Content & configuration
Example Swagger/OpenAPI definition:
Swagger-UI configuration options:
Describe the bug you're encountering
The parameters are expanded just fine if there is only one possible request object. But if you have more than one "type" of request that can be formulated, and you express this with a
oneOf
, the parameters are no longer expanded / exploded. The whole object is simply serialized as the value of the named parameter. Even if there is only a single object inside theoneOf
the exploding still gets messed up.To reproduce...
Here's a live example on codesandbox.
Steps to reproduce the behavior in the live example on codesandbox:
GET
operation in right preview panelTry it out
Execute
Expected behavior
The parameters should be exploded / expanded even when there are multiple "types" to choose from that are defined in an
anyOf
.Screenshots
The text was updated successfully, but these errors were encountered: