Feature request: fetchPolicy about axios-hooks

[simoneb]

I see what you mean. Yes it would make sense to have something like this, but because it would be quite some additional complexity to add to the package, which at the current time is overall quite simple, and because the workaround in your case is super simple as well, I wouldn't consider this a priority. I mean it's complexity added to the package versus a one line of code on the package user.

[simoneb]

Isn't this case already covered by the normal behavior of the hook together with the second item of the array returned by the hook invocation (sometimes called refetch) which allows you to issue the request again?

[stevewillard]

Yeah, I think that would work, but I was hoping to avoid explicitly recalling refetch.

Here's the scenario I'm working with:

I have a table of data with pagination controls, where the page is stored in the URL as a query parameter. I'm using this hook to parse/set that query parameter: https://github.com/pbeshai/use-query-params

So, I have something like this:

const [page = 1, setPage] = useQueryParam('page', NumberParam);

const [{ data, loading, error }, refetch] = useAxios({
    url: 'my_api_route',
    params: {
        page,
    },
});

When I click on a new page, I call setPage which updates the URL, which re-renders the component and the axios hook will fetch the new page of data.

If I navigate back to a page I have already seen, axios-hooks will read from the cache, but what I want is to read from the cache and also issue a network request. I could definitely achieve this by calling refetch as part of the onClick for the pagination control which calls setPage, but I was hoping to do this automatically. The issue with this is that it'll issue two API calls the first time a page is loaded (once for when the component re-renders with the new page, and the refetch call will trigger it again).