How we Redux — Part 3 (Domain)
Abhi Aiyer
7612

Thank you for writing up such a great series of articles!

I like the way that you use thunk to incorporate Meteor methods into the Redux flow. However, when I look at the console messages printed from redux-logger, those actions like addTodo, toggleTodo are not shown, which I think makes these changes hard to trace.

I’m thinking if adding a wrapper action to the callback of the method will be meaningful? Something like:

addTodo = (text) => {
return (dispatch) => {
Meteor.call('addTodo', text, (err, res) => {
if (!! err) dispatch(todoError(err));
else dispatch(todoAdded(res));
});
};
};

It adds lots of boilerplate though .. What do you think?

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.