Add caching for components?

[must]

How would we go about caching a list of articles that have been loaded when changing between pages.

[loreanvictor]

I think the best method would be caching the corresponding backend functions. for example look at this.

[must]

How would this work for paginated data? So yes it will reload things from the cache (which can create some inconsistencies eventually and that's another topic) but reloading the component would default to the first n articles, wouldn't it? And the user will still have to scroll to reload (from the cache).

[loreanvictor]

ok now I understand what you mean. well through navigation the old component is destroyed and a new instance is created. data that is displayed is an internal state of that component, stored inside its closure, which gets destroyed when the component is destroyed.

the only way around this would be for the component to store this state somewhere outside of its closure, so each new instance can pull it from there. localstorage for example would do, but perhaps for this purpose simply moving the state corresponding to loaded data outside of the component would suffice.