Personalizing the Pomodoro timer

Well, now that we can already sign in new users and log in the existing ones, probably we should think about taking advantage of our authentication mechanism because right now we are actually not doing anything with it. We just sign up and we just log in. Yes, we also can hide or show some content based on the user's authentication, but this is not enough. The whole point of all this effort was to be able to store and retrieve the user's custom configuration for the Pomodoro timer and the user's statistical data.

Until now, we have been using a hardcoded database object with the key test in order to access the user's data, but now, since we already have our real users, it's time to populate the database with real users' data and use it in our application. Actually, the only thing we have to do is to replace this hardcoded value with the actual user's ID. So, for example, our code to bind the config reference was looking like this:

// store/actions.js
bindConfig...