Add Shared preferences in the core module (Issue 56) #67
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
michaelbukachi
approved these changes
Mar 23, 2020
|
@wangerekaharun, the link, is private, i think it needs an invite |
|
Share your trello username, I will send the invitation |
|
@wangerekaharun jamamohamed6 |
|
Invitation Sent |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What is the Purpose?
Add Shared preferences in the core module
What was the approach?
As stated by @michaelbukachi on issue #56, was to create a
PreferencesImplclass that implements thePreferencesinterfaceAre there any concerns to addressed further before or after merging this PR?
Added a private method
editSharedPrefto avoid calling theapplymethod for every edit of the state. I think it will prevent unnecessary code duplication ofapplymethodMentions?
@wangerekaharun @chepsi @michaelbukachi
Issue(s) affected?
#56