Ensuring second-hand resource reads still trigger Suspense

[fabiospampinato]

Reading a memo that reads a resource could not trigger Suspense properly today, if the memo already executed and calling it just returns the old value.

[ramon18]

Hi,
Not sure if this is related, but I cannot make a functional based on the docs example.
It either don't run show the or does not render the fallback.

This is the only way I could make it work as I expected:

const App = () => {

  const resource = useResource ( () => {
    return new Promise<string>((resolve) => setTimeout(() => {
      resolve('Voby!');
    }, 3000));
  });

  return (
    <Suspense fallback={<p>Loading...</p>}>
      {() => resource ().value}
    </Suspense>
  );
}

Could you please hint where is the problem on the docs example?

Congrats for this amazing library!

[fabiospampinato]

@ramon18 I didn't understand the question, which code is not working or requires more explanation? 🤔

[ramon18]

If you try the Suspense example from the docs and implement the makeSomePromise, for example:

const makeSomePromise = () => new Promise<string>((resolve) => setTimeout(() => {
  resolve('Voby!');
}, 3000));

My expectation was:

Loading...
(...3 seconds later....)
Voby!

But It doesn't, maybe my expectation are wrong in first place...