Community
Participate
Working Groups
In bug 335440 we had an example of a breaking change to the user authentication data. I suspect this isn't the last time we will need to alter the format, so we should have a mechanism in place to handle migration of the data. I suggest: - Also write a property "UserRightsVersion" for each user with a simple integer value - AuthorizationService class reads the version, and delegates to a separate class to read the authorization data from preferences into a JSONObject (AuthorizationReaderV1, AuthorizationReaderV2, etc) - AuthorizationService always writes data in the "latest" format and sets the UserRightsVersion property to the latest version number.
Although we could probably get away with no migration this time, it is a good opportunity to get that infrastructure in place now.
I have released migration support for the "old" M4 format and the current format.