Dataframe transforms are not persistent across saves? #3449
fgeorgepar
started this conversation in
General
Replies: 2 comments
-
Hi @fgeorgepar, yes this is the intended behavior. We currently don't store/save any UI state across sessions. We may add an option to do so (storing in the URL params or the serialized file). How would you like this state stored and where? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi @mscolnick I think storing automatically storing the state with the autosaves would be ideal but whatever is the most feasible option should do (even if it's a manual call to a function that stores state in a separate file). Thanks for looking into this! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I opened up a new notebook and created a few dataframe transforms using mo.ui.dataframe() (i.e., filters, expand dict) expecting them to be persistent across saves of the notebook. I was surprised to open up the notebook later and had blank transforms with nothing selected. Is this the intended behavior or am I missing a configuration somewhere that persists these elements? Is it not possible to save the state of the notebook to capture these changes to filters or other transforms? Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions