Store user information in persistenceDirectory #1017
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Goal
Stores user information in the
persistenceDirectory
. If legacy user information is set inSharedPreferences
, it is migrated from there.Changeset
Client
and then deleted legacySharedPreferences
fileSharedPrefMigrator
to read user information, check whether a file exists on disk, and to provide a mechanism for deleting the legacy fileUserRepository
classUserStore
class which loads/saves the user, and migrates the legacy value fromSharedPreferences
UserState
so that it only emits an observable when its value is set, and is not responsible for loading the user from disk. TheUserStore
registers an observer onUserState
which persists the changed user value if requiredDeviceIdStore
so that it only callsloadDeviceId
on the first launch, rather than each timeuser
property toImmutableConfig
which mirrorsConfiguration#user
Testing
ClientTest
intoClientUserTest