News for hackers. Stuff that matters.
Re:Designing simpler React components by djfm on Saturday March 26, 2016 @10:23PM (#11368573)
> At least until you want asynchronous actions (and you will) in which case it seems to shrug and encourage using addons with side effects.

Imho there's nothing special with async actions and you don't necessarily need an addon, they're just actions arriving to the reducer later, and it can't see the difference. Your data fetching is no more async than a user clicking on a button.

Re:Designing simpler React components by svachalek on Saturday March 26, 2016 @10:38PM (#11368614)
Well, rather than getting into a debate on what constitutes "nothing special" or "side effect", I'll let the docs explain the details.

http://redux.js.org/docs/advanced/AsyncActions.html

Note however that it does say "This function doesn’t need to be pure; it is thus allowed to have side effects, including executing asynchronous API calls."

Re:Designing simpler React components by amackera on Sunday March 27, 2016 @01:55AM (#11369074)
Out of curiosity, would it be possible to be able to do async actions without side effects?
Re:Designing simpler React components by adyus on Sunday March 27, 2016 @02:34AM (#11369130)
setTimeout() ?
Re:Designing simpler React components by danmaz74 on Sunday March 27, 2016 @04:53AM (#11369383)
Creating a timeout modifies the global state and is therefore a side effect.