Is it ok to use autorun inside a lazyObservable fetch callback?

[jraoult]

Hi 👋,

I recently found myself using this pattern more and more in a web app context using with React. Let's say I have a list of items and each list has an id:

1. I want to react to a change when the route is updated (change of list)
2. I want to command a refresh of the list after a mutation deep down the component tree.
3. I want to stick to the previous loaded list as long as possible during a refresh/load to avoid flashing.

Turns out lazyObservable offers 2 and 3 out of the box and to implement 1 I used an autorun in the fetch callback that reacts to the mutation of observables used in a keyProvider function:

const createLazyList = (httpClient, keyProvider) =>
  lazyObservable((sink) => {
    autorun(() => {
      fetchList(keyProvider()).then((data) =>
        sink(observable(data))
      );
    });
  }, null);

Is it OK to do that or is there a better primitive for it?