Change `UserData` to `UserPreferences`
See original GitHub issue“Preferences” more accurately describes the data this model contains.
Also requires changing the *UserDataRepository
objects to *UserPreferencesRepository
Issue Analytics
- State:
- Created a year ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
UserDefaults | Apple Developer Documentation
The defaults system allows an app to customize its behavior to match a user's preferences. For example, you can allow users to specify...
Read more >User Preferences - Reasons for Change
ID; Active - When a reason for change is active, it can be selected as a reason for change when modifying user data...
Read more >How to store user data in Electron - Cameron Nokes
Most Electron apps need some sort of way to save user data. This could be user preferences (e.g. show/don't show notifications) or some...
Read more >Detecting Changes in User Preferences using Hidden Markov ...
We propose a HMM-based approach to change point detection in the sequence of user interactions which reflect significant changes in preference ...
Read more >Storing user settings with UserDefaults - a free Hacking with iOS
One common way to store a small amount of data is called UserDefaults , and it's great for simple user preferences. There is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@dturner renaming
UserData
toUserPreferences
will conflict withcom.google.samples.apps.nowinandroid.core.datastore.UserPreferences
that’s generated byuser_preferences.proto
I think we should pick another name 🤔Thanks for the suggestions. I’m inclined to leave as-is for now. It’s likely that we’ll store other information here in future and
UserData
is generic enough to accommodate that.