Interceptors aren't chained about use-http HOT 8 OPEN

@veloware I came across the same problem and solved very similar approach as you mentioned.
I think you can create a pull request with this change so it can be reviewed ?

from use-http.

@veloware how can you access the globalOptions?

from use-http.

@alon-green there is a 2nd arg you can pass to useFetch as a callback, its the first arg of that callback, e.g. -

useFetch(url, (globalOptions) => ({
   ...
    interceptors: {
      request: async ({ options }) => {
        globalOptions.interceptors?.request?.({ options });
        ...

from use-http.

@veloware thanks for the answer, but I already pass options in the useFetch, in nested hook, I need access to the option of the provider

from use-http.

in the case above though, the globalOptions is not passed to the callback, it's provided by the callback. Those will be the options that were set at the <Provider options={xxx}> level

from use-http.

But I can't access the provider, can't I take it from the context or something?

from use-http.

@veloware Let me try to create a CodesandBox of this

from use-http.

@alon-green here is the CodeSandbox https://codesandbox.io/s/usefetch-use-http-todo-list-app-managed-state-forked-x1ru0p?file=/src/index.js. If this code sandbox is clarifying solution to your problem or still, it is a problem. now you can modify the code sandbox to help us to understand better. hopefully we can solve it.

@veloware

from use-http.