Adding initWithSuiteName support for UserDefaults.#7
Adding initWithSuiteName support for UserDefaults.#7henrylilei wants to merge 2 commits intodsibiski:masterfrom
Conversation
Update README.md
|
@dsibiski any feedback? Thanks! |
|
@henrylilei I was actually testing this out last night. It was working well until I tried to use the Using the Also, it seems that since this is only an instance and not a singleton, do you set the suite name every time you need to use it? How have you been using it? |
Remove the false claim about being able to go back to standardUserDefaults.
|
@dsibiski You are correct, I just tested it and it won't allow you to go back to standardUserDefaults. I had removed the false claim. If you think the going back to standard scenario is important, I can add a new method to provide standardUserDefaults access. My iOS app is using multiple user defaults to separate the internal data logic, thus we have different underlying plist file names. Every time we need to fetch some data from these plists, we set the corresponding file name and grab the values from it. |
|
Is it possible to get this merged and added as a new version in npm? |
Thanks!