Skip to content
New issue

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

[Bug]: Unable to set explode to false for a query parameter #4165

Closed
4 tasks done
Sylvain2703 opened this issue Aug 13, 2024 · 3 comments
Closed
4 tasks done

[Bug]: Unable to set explode to false for a query parameter #4165

Sylvain2703 opened this issue Aug 13, 2024 · 3 comments
Assignees
Labels
bug Something isn't working needs-area

Comments

@Sylvain2703
Copy link
Contributor

Describe the bug

According to the OpenAPI 3.0 guide, the default for the explode option is true (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 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.

Reproduction

Playground Link

Checklist

@Sylvain2703 Sylvain2703 added the bug Something isn't working label Aug 13, 2024
@timotheeguerin
Copy link
Member

oh ouch

@timotheeguerin
Copy link
Member

Will be release in openapi 0.59.1

@Sylvain2703
Copy link
Contributor Author

Great, thank you very much 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-area
Projects
None yet
Development

No branches or pull requests

2 participants