Currently, if the settings change, the user's settings could be overwritten or ignored as they were valid for an older settings configuration. To avoid this behavior, the settings should be migrated to a newer configuration. But, we need to know what settings version was valid when the settings were set by the user. Therefore, we have to give each settings configuration a unique identifier and store the valid one locally on the user's browser. If the identifier of the settings configuration do not match the stored one, the old settings should be migrated to the new settings format as possible.
Goals
Settings unique identifier (preferably an integer that is simply increased by one on each settings change)
Automatically migrate the settings if there are of an older version
# Settings backward compatibility
Currently, if the settings change, the user's settings could be overwritten or ignored as they were valid for an older settings configuration. To avoid this behavior, the settings should be migrated to a newer configuration. But, we need to know what settings version was valid when the settings were set by the user. Therefore, we have to give each settings configuration a unique identifier and store the valid one locally on the user's browser. If the identifier of the settings configuration do not match the stored one, the old settings should be migrated to the new settings format as possible.
## Goals
- Settings unique identifier (preferably an integer that is simply increased by one on each settings change)
- Automatically migrate the settings if there are of an older version
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Settings backward compatibility
Currently, if the settings change, the user's settings could be overwritten or ignored as they were valid for an older settings configuration. To avoid this behavior, the settings should be migrated to a newer configuration. But, we need to know what settings version was valid when the settings were set by the user. Therefore, we have to give each settings configuration a unique identifier and store the valid one locally on the user's browser. If the identifier of the settings configuration do not match the stored one, the old settings should be migrated to the new settings format as possible.
Goals