Oleg Kuzava

indeed, there is try/catch inside `useGet` - but in fact, it doesn't re-throw error like it is done in `useMutate`. @fabien0102, was it designed like that? I also see this...

btw, there is some input here: https://github.com/contiamo/restful-react/issues/235

> I have a scenario in where I need to make many submissions in a component, each for a different id, which is a path parameter. It'd be so nice...

one of options: ``` const api = new Api({ secure: true, baseURL: process.env.NEXT_PUBLIC_API_BASE_URL, securityWorker: accessToken => accessToken ? { headers: { Authorization: `Bearer ${accessToken}` } } : {}, }); //...

this could be achieved with https://github.com/ljharb/qs you can pass this to `requestParams` (the last argument) ``` { paramsSerializer: params => qs.stringify(params, { arrayFormat: 'brackets' }), }, ``` see more options:...

as workaround, you can remove default headers from the api instance. ``` const api = new Api(); api.instance.defaults.headers.put = {}; api.instance.defaults.headers.post = {}; api.instance.defaults.headers.patch = {}; api.auth.login() ``` now, `type:...

Actually, it's already fixed in https://github.com/acacode/swagger-typescript-api/commit/94087eca8ff3d717fec054725c159e8f9f5d9cb8 (upcoming release)

the same here - I see white-screen without any errors when call ```js history.replace({ search: '?whatever=1' }); ``` Issue appears after upgrading to v5

> What do you think @ApacheEx ? Hi, probably we can add a public method instead, smth like: setSupportRequestState

Yes, please 👌