Skip to content

Commit b2ef009

Browse files
committed
2 parents 59ddf6c + 69bb92c commit b2ef009

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

apps/docs/content/docs/request-and-response-helpers.mdx

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -111,20 +111,19 @@ The `resultMode` option dictates how CallApi processes and returns the final res
111111

112112
### The `fetchApi` Mode
113113

114-
The `fetchApi` mode is designed for scenarios where you want most of the library's benefits (URL resolution, plugins, hooks) don't want any internal parsing of data to occur, just like the `Fetch Api`.
114+
The `fetchApi` mode is designed for scenarios where you want most of the library's benefits (URL resolution, plugins, hooks) don't want any internal parsing of the response body to occur, just like the `Fetch Api`.
115115

116116
When set to `fetchApi`:
117117

118118
1. **No Parsing**: The library will not attempt to read or parse the response body.
119-
2. **No Validation**: Both request-option validation and response/error-data validation are skipped.
120-
3. **Internal Optimization**: Minimal overhead as it simply returns the response object immediately after the fetch/middleware phase.
119+
2. **No Validation**: Both data error-data validation are skipped.
121120

122121
<Callout type="warn">
123122
By default, simplified modes (`"onlyData"`, `"onlyResponse"`, `"fetchApi"`) do not throw errors.
124123
Success/failure should be handled via hooks or by checking the return value (e.g., `if (data)` or `if
125124
(response?.ok)`).
126125

127-
To force an exception instead, set `throwOnError: true`.
126+
To force an exception, set `throwOnError: true`.
128127

129128
</Callout>
130129

0 commit comments

Comments
 (0)