-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't lose map options when upgrading or codepush-ing #4849
Comments
Whatever solution we come up with should be capable of generalizing to other pieces of local state that we want to survive across upgrades/codepushes since this kind of request will inevitably come up again. |
Here's some past history that's probably relevant. There was a ticket ...
... which had a similar problem. There was a discussion ...
... on how to fix it. There was some talk about (creating and) preserving a dedicated part (ie. 'settingsStore'?) of the MST tree across upgrades. But this was short-circuited by just storing in So, for this ticket, I guess we could revive the discussion about 'settingsStore' or just store it in |
@bengtan Yes, I solved it in the same way as I did with 'invisible' mode before. |
QA notes: This ticket should be tested by upgrading from a version which already includes this ticket. |
From https://github.com/hippware/collaboration/issues/22#issuecomment-586364539:
I believe this is referring to the
mapOptions
setting in HomeStore. It's lost upon upgrade (or codepush). It'd be nice to preserve it across upgrade or codepush.The text was updated successfully, but these errors were encountered: