[Feature]: Retain data cache for parts widgets about appsmith HOT 6 OPEN

@rennzhang what type of data are you looking to cache? You can use the storeValue function to save data in the local storage.

from appsmith.

Simply put, I hope that the page switch will not re-render the component. I tried some react-route caching solutions, but it didn't work

For example, page a has a table component. I enter some query conditions and search for data. Then I jump to page b and return to page a. I hope that page a will not be refreshed, that the data will not be retrieved, and that I will keep the query conditions I entered before.

from appsmith.

@rennzhang that is currently not possible

from appsmith.

@Nikhil-Nandagopal Thank you for your answer. I spent a few days understanding the component rendering mechanism of this project, which is indeed very complex. However, I am not familiar with React enough, so I would like to ask about the general reason

from appsmith.

The general reason is that each page is garbage collected after it's navigated away from to ensure that it doesn't consume memory. Appsmith is generally used for live dashboards where data changes and so it makes sense to fetch the data again.

from appsmith.

I fully understand that it makes sense to have him rerender. Too much caching will cause a lot of memory to consume, and maybe the data state of the component is incorrect... But I still want to ask, if I only make modifications to a few components, such as table and list components, so that it retains data when switching pages, or recovers data from cache, is there any feasible way?

I tried to store cached widgetStaticProps here. Judging from the print log, it will initially be applied to the component, but will eventually be overwritten by the original props.

from appsmith.