Open bengtan opened 4 years ago
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 clientData
instead.
So, for this ticket, I guess we could revive the discussion about 'settingsStore' or just store it in clientData
.
@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.