-
Notifications
You must be signed in to change notification settings - Fork 136
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
fix(ui): localstorage compatibility issue #930
fix(ui): localstorage compatibility issue #930
Conversation
LGTM, some suggestions:
|
Thanks for the suggestion. Considering that cleaning up localstorage after a release version change is too frequent on the cloud. Maybe we should simply use the |
is 'on cloud' means users always see the latest version? If so, two entries for the old one and the new one should be enough. However I prefer to mark a version having breaking change of the localstorage schema manually and then migrate automatically rather than use a new entry every time update, which lead to the risk that users lose some settings even when there is no conflict between two versions. Just a suggestion. |
How about this? |
09a77af
to
565209d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly LGTM! Let's prioritize this PR so that it can be carried in 4.0.14.
a44c13d
to
df93869
Compare
b12fd74
to
857afcc
Compare
This comment has been minimized.
This comment has been minimized.
a8301e0
to
804db1a
Compare
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 804db1a
|
close #902
related: docs
Local storage key will have release-version suffix by using
useCompatibilityLocalstorage
helper function.