-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose an api for entirely non-null preferences #122
Comments
Can you describe some examples where the Kotlin interop can be improved? |
Basically I wouldn't have to be reading (for example) |
are you on 2.0.0? i thought null was already banned in preferences now. |
oops, no, still on an older version. |
looks like this has been resolved, so sorry. I checked issues but not the latest code, oops. |
It'd be very nice for cases where you don't have a null default and don't ever set null into a preference to have a clean non-null version of Preference. Would make kotlin interop better as well.
Looking through issue history, seems like there's a lot of conflicting threads pulling the library around nulls. Rather than force a change to existing Preferences a new set of NonNullPreference (though with a better name?) methods would be an easy change.
I could whip up a pull if this is appealing.
The text was updated successfully, but these errors were encountered: