Versioned Preference System

[Dhruv-0-Arora]

AARD-2025

Symptom

After removing/adding something to the preference system during development, users' preferences will be 'outdated' which can cause misalignments between what is stored in their local storage cache and

Task

Add a versioning to the Preference System that will enable Synthesis to migrate between versions when the production has been pushed to prevent users from running into issues when a new version is released and their local preferences are outdated.

Solution

Added a version to global preferences to determine whether a client's versioning system is outdated & a migration system to translate the old preferences to be compatible with the new version of fission.

Verification

Manually changing the version of the preference system and modifying any of the keys of the preferences themselves.

---

Before merging, ensure the following criteria are met:

• All acceptance criteria outlined in the ticket are met.
• Necessary test cases have been added and updated.
• A feature toggle or safe disable path has been added (if applicable).
• User-facing polish:
  • Ask: "Is this ready-looking?"
• Cross-linking between Jira and GitHub:
  • PR links to the relevant Jira issue.
  • Jira ticket has a comment referencing this PR.