"Global" persistence and Graph persistence

[eidsobr]

My web apps are almost always multi-page with dozens to hundreds of input fields. I'm always setting all possible components to have persistence=True. Three things would be nice.

1. some global setting for the app to persist as much as possible.
2. adding the ability to persist graphs. My apps have lots and lots of "intermediate" outputs as users refine input settings. Results "over here" impact results "over there" and users want to click back and forth a lot. The "manual" caching technique is painful and taxing. E.g.,
   https://stackoverflow.com/questions/63611740/how-to-persist-state-of-plotly-graph-in-dash-app
3. As has been discussed in many forums, "fixing" the issue where component values are updated via callbacks not persisting.
   E.g., https://community.plotly.com/t/losing-persistence-value-on-refresh-when-input-value-updated-using-callback/39813

[AnnMarieW]

@eidsobr
These are great suggestions and would be a nice addition to dash. It's likely that any solution would be made available in dash-labs first in order to get community feedback.

We'll keep this issue open to make sure this stays on the radar and to collect other comments on this topic.

Note that your third point: "component values updated via callbacks not persisting" is a bug and there's an open pull request to fix it. 🎊