These are chat archives for reflux/refluxjs

19th
Nov 2015
Mikael Brassman
@spoike
Nov 19 2015 09:04
@yonatanmn the reason I've been holding off adding a setState to stores is that it will dictate how immutability is done. some users prefer to use their own immutable library (immutablejs, mori, etc.), so with Reflux coming with their own means bloat for these users.
yonatan
@yonatanmn
Nov 19 2015 09:31
maybe you can add an option to change the setState function - something similar to what you've done with the event emitter
Mikael Brassman
@spoike
Nov 19 2015 09:40
yeah, I was thinking about replacing the event emitter at some point to a simpler pubsub mechanism
and reflux-promise got made so I didn't have to do the same with promises, as that feature switching I implemented violated CSP (through "crafty" use of eval).
yonatan
@yonatanmn
Nov 19 2015 09:49
anyway - I think that opinionated setState (changeable or not) as an option is ok, and those who want to do it their own way should just alter state the way they want, ignoring setState, taking care of triggering themselves
(like react's setState which is opinionated by default...)