Skip to content

Commit

Permalink
add more documentation in data persistence readme about vis builder p…
Browse files Browse the repository at this point in the history
…ersistence

Signed-off-by: abbyhu2000 <abigailhu2000@gmail.com>
  • Loading branch information
abbyhu2000 committed Jan 4, 2023
1 parent 912a8d5 commit 78baaf7
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions docs/plugins/data_persistence.md
Original file line number Diff line number Diff line change
Expand Up @@ -196,6 +196,8 @@ There are two types for data persistence:
4. In `useEditorUpdates()`, we use the saved appState to load the visualize editor
5. Since we implement state management in Vis Builder with redux store, the app state persistence implementation for vis builder is also different than other plugins. While the global state persistence is the same, we implement app state persistence without using any state containers or state syncing utils. For the actual visual data, we directly hook up redux store with `OsdUrlStateStorage` to sync the values by using `saveReduxState()` and `loadReduxState()`. For app filter and query, since they are part of the app states but not part of the redux store, we directly hook up their state managers from data plugin with `OsdUrlStateStorage` and `connectStorageToQueryState()`.
# Refresh
When we refresh the page, both app state and global state should persist:
Expand Down

0 comments on commit 78baaf7

Please sign in to comment.