Skip to content

Fix: query param array serialization #223

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

Merged
merged 2 commits into from
Apr 4, 2021

Conversation

Styn
Copy link
Contributor

@Styn Styn commented Apr 4, 2021

This is a fix for #222
I also renamed the function to make that part of the code it bit clearer.

@js2me
Copy link
Member

js2me commented Apr 4, 2021

Hello @Styn !
Thank you for your fix!

@js2me js2me merged commit 6ae8d41 into acacode:next Apr 4, 2021
@js2me js2me mentioned this pull request Apr 4, 2021
js2me added a commit that referenced this pull request Apr 4, 2021
* BREAKING_CHANGES: remove default `json` format of the response type

* fix: missing `schema.$ref` in inline enum schemas

* Allow passing custom fetch function (#218)

* Allow passing custom fetch function

* Fixing a mistake

* Using ApiConfig instead of second param

* fix: tests

* chore: refresh schemas

* Fix: query param array serialization (#223)

* make the query params serialization conform to the default open api specs

* uri encode second part

Co-authored-by: stijn.lammens <[email protected]>

* docs: update CHANGELOG

* fix: unused E generic type

* chore: refresh generated test schemas

* bump: up version to 8.0.0

Co-authored-by: Sushruth Shastry <[email protected]>
Co-authored-by: Stijn Lammens <[email protected]>
Co-authored-by: stijn.lammens <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants