Feature suggestion: SharedPreferences.putAll keys and values about android-ktx

[f2prateek]

Instead you could have something an extension function on SharedPreferences.Editor —put(key: String, val: Any?). This would do the type switch internally, with some special cases:

• null -> deletes instead of setting the key
• non-SharedPreferences supported type -> throws an exception.

[JakeWharton]

We'd do overloads. No need to switch.

…

On Mon, Feb 5, 2018, 6:56 PM Prateek Srivastava ***@***.***> wrote: Instead you could have something an extension function on SharedPreferences.Editor —put(key: String, val: Any?). This would do the type switch internally, with some special cases: - null -> deletes instead of setting the key - non-SharedPreferences supported type -> throws an exception. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#153 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAEEEWTWNlfflftiVSL7Vb-tE4BePrg_ks5tR5UggaJpZM4R6Ph6> .

[JakeWharton]

Does this really add much value? It causes allocation of varags and pairs for something that isn't much less verbose than the existing edit-with-lambda approach. I'd rather figure out how to make the actions on the editor simpler if possible than something like this.

[jczerski]

You are right, this is not the optimal solution. At the same time, pasting data due to their type is exhausting.

Regards,
Jack

[JakeWharton]

And delete is already remove("key") which is hard to improve upon.