provide seamless migration for existing users to upcoming major version #26

New Issue

michael · 2026-01-19T18:31:57Z

michael commented

2026-01-19 18:31:57 +00:00

Originally created by @abhijithvijayan on GitHub.

Set up a function to update extension settings (from browser local storage)
to the new settings keys
Map the keys like autoCopy : true to the new

"settings": {
   "autocopy": true,
   ...
}

on the installation / initialization of new major version.

Remove this feature after all the users have switched to the new major version

Without this mapping, the extension will UX issues for those who are using it currently.

Originally created by @abhijithvijayan on GitHub. - [x] Set up a function to update extension settings (from browser local storage) to the new settings keys Map the keys like `autoCopy : true` to the new ``` "settings": { "autocopy": true, ... } ``` on the installation / initialization of new major version. - [ ] Remove this feature after all the users have switched to the new major version Without this mapping, the extension will UX issues for those who are using it currently.

michael added the topic: ux status: on hold type: maintenance release: minor breaking change labels 2026-01-19 18:31:57 +00:00

michael closed this issue

2026-01-19 18:31:57 +00:00

michael commented

2026-01-19 18:31:58 +00:00

@abhijithvijayan commented on GitHub:

Migration actions are performed once on popup open(once extension is updated to v4.x.x) if previous keys exist on browser local storage.

The code can be removed once all the users receive the update.
I have tested with basic options enabled as well as advanced options(like custom host) enabled. It works. :)

I will leave this issue open if someone runs into issue on migration.

@abhijithvijayan commented on GitHub: Migration actions are performed **once** on popup open(once extension is updated to v4.x.x) if previous keys exist on browser local storage. The code can be removed once all the users receive the update. I have tested with basic options enabled as well as advanced options(like custom host) enabled. It works. :) I will leave this issue open if someone runs into issue on migration.

michael commented

2026-01-19 18:31:58 +00:00

@abhijithvijayan commented on GitHub:

Current fields in local storage of almost all users

{
	"URL_array": [],
	"host": "https://google.com",
	"key": "this is the api key",
	"pwd": "password",
	"userOptions": {
		"autoCopy": true,
		"devMode": true,
		"keepHistory": true,
		"pwdForUrls": true
	}
}

Migrate to

{
	"settings": {
		"advanced": true,
		"apikey": "he;;obaby",
		"customhost": "https://google.com",
		"history": false
	}
}

@abhijithvijayan commented on GitHub: Current fields in local storage of almost all users ``` { "URL_array": [], "host": "https://google.com", "key": "this is the api key", "pwd": "password", "userOptions": { "autoCopy": true, "devMode": true, "keepHistory": true, "pwdForUrls": true } } ``` Migrate to ``` { "settings": { "advanced": true, "apikey": "he;;obaby", "customhost": "https://google.com", "history": false } } ```

michael commented

2026-01-19 18:31:58 +00:00

@abhijithvijayan commented on GitHub:

Completed and removed migration code in https://github.com/thedevs-network/kutt-extension/pull/138

@abhijithvijayan commented on GitHub: Completed and removed migration code in https://github.com/thedevs-network/kutt-extension/pull/138

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: thedevs-network/kutt-extension#26