Closed levibostian closed 6 years ago
After some thoughts on this, I am going to skip option (4) above. I do not see a big reason to add multiple databases right now. Technically, you can hack Wendy right now for multiple user's logged in at once and separate their data. No need for multiple databases. As long as it aligns with the correct user, it doesn't matter.
As far as clearing data, I have added that ability and it will be released with the newest release of the library.
Use case: A user logs into your app. They do some tasks that are performed by Wendy. The user logs out and another user logs in.
What do you do?
There are pros and cons to all of the options above, but it all depends on how you are building your app. I don't want to be opinionated, so I should add functionality and give the power to the user on how to do each.
Here is the action plan for all of the above options:
Wendy.shared.getAllTasks()
to check if it's empty. You can then add a task runner listener and watch progress if you wish on the runner as it goes through tasks. Done!dataId
for aPendingTask
have a suffix for the user ID of a user. Done!