added the initialization function of the dataSource called it on the …

[Amoodaa]

…app.componentDidMount and only when the user is logged

relates #137

[11janci]

ok I think I finally understand, you're trying to do a data store for data shared between components, similar to Redux.. Got confused by the dataSource name and the combination with the API 🙂

That's not a bad idea, of course in practice you would use an existing solution like Redux instead of doing your own, but outside of that, this is a nice implementation! 👍
My only suggestion would be to separate the concerns:

• take the API outside of the store, do not mix it
• allow arbitrary object for the state (instead of having fixed structure that contains users, channels, etc.)

Doing that would give you a generic store that you can reuse for different use cases and across projects. So instead of for example the init() function where you call some application-specific APIs, there would be just one function to update the data:

update: newState => {
    state = newState; // just an example, you would have to properly merge the objects
    notifySubscribers(state);
}

This function would be called instead of component's setState in existing API calls.

api.getChannels().then(res => dataStore.update({ channels: res.channels }));

And if you want to simplify it, so that you don't have to call the update function everywhere, you can couple the store with the APIs in a separate module

// this will update the store automatically
dataStoreApiWrapper.getChannels();

The problem with this solution is that it calls setState for every subscribed component every time the data store changes, which means that every component will get re-rendered even when its state necessarily didn't change. There are ways to deal with that, but overall, you're on the right path, nice job guys..
Hope this all makes at least a bit of sense 😆