feat(resourcefactory): added dispose option to ResourceFactory.use

[jacob-ebey]

This change allows for things like page transitions to not bust the cache and reload from there on
back button. Does not modify existing behavior.

[overlookmotel]

Thanks for this.

Hmm. I understand the use case, but the problem I foresee is that the data will then never be disposed of. This has two problems I can think of:

1. The cache would grow and consume memory with no limit.
2. Once loaded, data can never be re-loaded, so stale data will stick around forever. They'd be no way to fetch fresh data without a hard reload (i.e. "Reload" button).

Do you have thoughts on how to counter either of these problems?

[jacob-ebey]

@overlookmotel I'll have to look into it further. For further context, here is the use-case I'd like to enable:

1.) Server SSR's and stores in CDN edge edge cache
2.) User transitions to page 2 client side and fetches data client side skipping SSR on the Server
3.) User client side transitions back to initial SSR'd page via back button (should not trigger client side fetch as data should persist in cache)

Here is an example of the current behavior: https://pwrc-react.vercel.app/examples/ecom-example/
(you may have to slow down network calls or something to visually see the issue, but you can see it in the network logs). This is really just chasing any performance gains that are left.

Initial SSR'd load of home page loading client only assets:

Transition to PDP page properly loads assets that would have been in SSR'd response client side:

Transition back to home page from PDP unnecessarily loading data available in SSR'd response (yellow is SSR'd data not fetched in initial page load):

[overlookmotel]

So is the idea that the data is static and never ever changes?

[jacob-ebey]

@overlookmotel exactly. SSR'd data should remain static unless a manual invalidation action is taken.