Skip to content
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

Migrating browser data in different versions of Akita #106

Open
sharon-wang opened this issue Dec 31, 2020 · 1 comment
Open

Migrating browser data in different versions of Akita #106

sharon-wang opened this issue Dec 31, 2020 · 1 comment
Labels
data Akita extension data storage, retrieval, organization enhancement New feature or request

Comments

@sharon-wang
Copy link
Member

Currently, anytime we change the shape of the data being stored by Akita, the user needs to delete the extension and install Akita from scratch. This is pretty terrible since the user has to lose all of their data!

To address this problem, we need to start versioning our data so that we can apply the appropriate transformations to the data between different versions of the extension.

@sharon-wang
Copy link
Member Author

Maybe we'll want to give users a way to download their raw data in JSON format, so they can hold a copy of their data if they choose to install a newer version of Akita that doesn't have data migration yet. In the future, along with the data migration implementation, we can give users the ability to upload their raw Akita data JSON, which we then transform to the data format compatible with the installed version of Akita.

@sharon-wang sharon-wang added enhancement New feature or request and removed priority 1 Highest priority labels Mar 17, 2021
@sharon-wang sharon-wang added the data Akita extension data storage, retrieval, organization label Apr 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data Akita extension data storage, retrieval, organization enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant