Skip to content
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

Change name? #13

Open
russhwolf opened this issue Jan 26, 2019 · 6 comments
Open

Change name? #13

russhwolf opened this issue Jan 26, 2019 · 6 comments

Comments

@russhwolf
Copy link
Owner

Kevin called me out in a podcast and said the name Multiplatform Settings isn't catchy enough. I've had this thought as well but I haven't yet come up with anything I like better. Leaving this here to track the possibility of changing it and potentially source ideas.

@kpgalligan
Copy link

I have no idea. I'm not great with names either.

@mustafaozhan
Copy link

Definitely agree with a change :) it is confusing if you have already SettingsView/SettingsFragment/SettingsViewController and plus a SettingsViewModel (which can be possible in many apps)

Then you want to use this library for entire app persistence and created a SettingsRepository. Upps! It will be used in entire app, not only in settings screen :)

@kurthuwig
Copy link

What about

  • KnobsAndLevers (something catchy for "settings")
  • PersistentKeyValueStore (which is what is actually does)

My main point is, that the library does not set anything or change any settings outside of itself. So why call it "settings"?

@CaelumF
Copy link

CaelumF commented Oct 10, 2023

It could be used for settings, and that's the use case it's designed around, which does probably have implications. I like non-catchy primary names.

How about "multiplatform-kv-settings"

@mustafaozhan
Copy link

mustafaozhan commented Oct 10, 2023

Ohh, years after you just reminded me @CaelumF 🙂 I have already got used to it but could be just Persist or Persistence too.

Also, @russhwolf this can be converted to discussion, Probably even discussions was not announced when this issue is created 🙂

@josegbel
Copy link

kase - to maintain kotlin's theme of using puns that contain the letter k.

Screenshot 2023-10-12 at 16 19 10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants