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
You can implement your own`httpClient`. This is useful if you need to extend the default `httpClient` methods with extra functionality, or replace it altogether.
236
+
You can provide a custom`httpClient` instance. This is useful if you need to extend the default instance with extra functionality, or replace it altogether.
237
237
238
238
```js
239
239
import { client } from'client/client.gen';
@@ -243,7 +243,7 @@ client.setConfig({
243
243
});
244
244
```
245
245
246
-
You can use any of the approaches mentioned in [Configuration](#configuration), depending on how granular you want your custom client to be.
246
+
You can use any of the approaches mentioned in [Configuration](#configuration), depending on how granular you want your custom instance to be.
You can implement your own`httpClient`. This is useful if you need to extend the default `httpClient` methods with extra functionality, or replace it altogether.
236
+
You can provide a custom`httpClient` instance. This is useful if you need to extend the default instance with extra functionality, or replace it altogether.
237
237
238
238
```js
239
239
import { client } from'client/client.gen';
@@ -243,7 +243,7 @@ client.setConfig({
243
243
});
244
244
```
245
245
246
-
You can use any of the approaches mentioned in [Configuration](#configuration), depending on how granular you want your custom client to be.
246
+
You can use any of the approaches mentioned in [Configuration](#configuration), depending on how granular you want your custom instance to be.
You can implement your own`axios` instance. This is useful if you need to extend the default`axios` instance with extra functionality, or replace it altogether.
216
+
You can provide a custom`axios` instance. This is useful if you need to extend the default instance with extra functionality, or replace it altogether.
Interceptors (middleware) can be used to modify requests before they're sent or responses before they're returned to your application. They can be added with `use`, removed with `eject`, and updated wth `update`. The `use` and `update` methods will return the id of the interceptor for use with `eject` and `update`. Fetch API does not have the interceptor functionality, so we implement our own. Below is an example request interceptor
149
+
Interceptors (middleware) can be used to modify requests before they're sent or responses before they're returned to your application.
150
+
151
+
They can be added with `use`, removed with `eject`, and updated wth `update`. The `use` and `update` methods will return the ID of the interceptor for use with `eject` and `update`. Fetch API does not have the interceptor functionality, so we implement our own.
You can implement your own`fetch`method. This is useful if you need to extend the default `fetch` method with extra functionality, or replace it altogether.
294
+
You can provide a custom`fetch`instance. This is useful if you need to extend the default instance with extra functionality, or replace it altogether.
287
295
288
296
```js
289
297
import { client } from'client/client.gen';
@@ -295,7 +303,7 @@ client.setConfig({
295
303
});
296
304
```
297
305
298
-
You can use any of the approaches mentioned in [Configuration](#configuration), depending on how granular you want your custom method to be.
306
+
You can use any of the approaches mentioned in [Configuration](#configuration), depending on how granular you want your custom instance to be.
Interceptors (middleware) can be used to modify requests before they're sent or responses before they're returned to your application. They can be added with `use`, removed with `eject`, and updated wth `update`. The `use` and `update` methods will return the id of the interceptor for use with `eject` and `update`. Fetch API does not have the interceptor functionality, so we implement our own. Below is an example request interceptor
133
+
Interceptors (middleware) can be used to modify requests before they're sent or responses before they're returned to your application.
134
+
135
+
They can be added with `use`, removed with `eject`, and updated wth `update`. The `use` and `update` methods will return the ID of the interceptor for use with `eject` and `update`. Fetch API does not have the interceptor functionality, so we implement our own.
You can implement your own`fetch`method. This is useful if you need to extend the default `fetch` method with extra functionality, or replace it altogether.
277
+
You can provide a custom`fetch`instance. This is useful if you need to extend the default instance with extra functionality, or replace it altogether.
270
278
271
279
```js
272
280
import { client } from'client/client.gen';
@@ -278,7 +286,7 @@ client.setConfig({
278
286
});
279
287
```
280
288
281
-
You can use any of the approaches mentioned in [Configuration](#configuration), depending on how granular you want your custom method to be.
289
+
You can use any of the approaches mentioned in [Configuration](#configuration), depending on how granular you want your custom instance to be.
You can implement your own`$fetch`method. This is useful if you need to extend the default `$fetch` method with extra functionality, or replace it altogether.
248
+
You can provide a custom`$fetch`instance. This is useful if you need to extend the default instance with extra functionality, or replace it altogether.
249
249
250
250
```js
251
251
import { client } from'client/client.gen';
@@ -257,7 +257,7 @@ client.setConfig({
257
257
});
258
258
```
259
259
260
-
You can use any of the approaches mentioned in [Configuration](#configuration), depending on how granular you want your custom method to be.
260
+
You can use any of the approaches mentioned in [Configuration](#configuration), depending on how granular you want your custom instance to be.
0 commit comments