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
fix(fetch): respect OpenAPI 3.0 explode default value for query params (#2143)
* fix(fetch): respect OpenAPI 3.0 explode default value for query params
* feat: add override.fetch.explode option for backward compatibility
* fix: make includeHttpResponseReturnType optional in FetchOptions
* docs: move the document to output.md
Copy file name to clipboardExpand all lines: docs/src/pages/reference/configuration/output.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -960,6 +960,15 @@ Default: `true`
960
960
When using `fetch` for `client` or `httpClient`, the `fetch` response type includes http status for easier processing by the application.
961
961
If you want to return a defined return type instead of an automatically generated return type, set this value to `false`.
962
962
963
+
##### explode
964
+
965
+
Type: `Boolean`.
966
+
Default: `false`
967
+
968
+
By default, the `fetch` client follows the OpenAPI specification for query parameter explode behavior. This means that query parameters will be exploded unless explicitly set to `false` in the OpenAPI schema.
969
+
970
+
If you want to maintain backward compatibility with the previous behavior (where only parameters with `explode: true` are exploded), you can set this value to `true`.
0 commit comments