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
Starting with TypeSpec 0.59.0, there is no way to produce explode: false for a query parameter with the OpenAPI 3.0 emitter.
When explicitly defining @query(#{ explode: false }), TypeSpec wrongly considers that the default value is false and therefore does not generate the explode: false property in the OpenAPI file. As a result, the explode option is always understood as true in Swagger UI.
Describe the bug
According to the OpenAPI 3.0 guide, the default for the
explode
option istrue
(unlike for path parameters and headers).Starting with TypeSpec 0.59.0, there is no way to produce
explode: false
for a query parameter with the OpenAPI 3.0 emitter.When explicitly defining
@query(#{ explode: false })
, TypeSpec wrongly considers that the default value isfalse
and therefore does not generate theexplode: false
property in the OpenAPI file. As a result, theexplode
option is always understood astrue
in Swagger UI.Reproduction
Playground Link
Checklist
The text was updated successfully, but these errors were encountered: