Imperatively refresh atomFamily

What would be the best way to imperatively refresh an atomFamily?

Let’s say I have following case, where I use get(updateAtomFamily) in order to track it as dependency in the atomFamily so that I trigger the fetch imperatively:

export const fetchAtomFamily = atomFamily(
  (param) => async (get) => {
    get(updateAtomFamily);
    const { data } = await getData({
      param1: param.param1,
      param2: param.param2,
    });
  },
  null,
  deepEqual
);

export const updateAtomFamily = atom(0);

Then my idea was to imperatively useUpdateAtom in my component as a refresh function like this:

  const refresh= useUpdateAtom(updateAtomFamily);

and then have the imperative call:

<button onClick={() => refresh(prev => prev + 1)}>refresh</button> 

However, when I trigger the refresh function, I get following error:

Uncaught Error: atom state not found. possibly a bug.

In my opinion however, even if this approach worked, it feels sluggish and cumbersome to me. It would be extremely helpful if the API had a native approach to re-fetch async atoms 😃

[jcoussard]

I really like this library! While I’m still trying the figure out its quirks, I figured solving a puzzle is a good way to learn.

Here is my attempt at it: https://codesandbox.io/s/cool-firefly-xhyc2

Is it a good way to solve that problem? I’m wondering whether const postsAtom = atom(fetchPosts()); is a good practice or not since it initialize the atom with a promise.

(PS it seems codesandbox’s refresh and Jotai don’t play along well, you might get the atom state not found. possibly a bug. error after editing the code, but it’ll work fine after reloading the in-page browser… still I’m curious what might cause it.)

[fkocovski]

I like your approach. For the moment I decided to stick to the empty atom variant and fill it with useEffect. I also tried the approach of having a primitive refresh atom with an initial value of 0 and use that as a dependency in the async get part and increment that one in order to trigger a re-fetch. That works now flawlessly in 0.7.3!