Bus vs No Bus Usage Question about react-bacon-todomvc HOT 2 CLOSED

Hi @dqdinh and sorry for delayed answer. I completely missed this issue... Sorry about that.

Yeah I know that Buses/Subjects are considered as bad practice in FRP but in React's case they are unfortunately the only way create actions from UI. The reason is that event streams must be known when building the application state ("addItem", "remove", ...) but the UI is instantiated ad hoc ("add item" button may not be visible during the first render).

Thus the following circular dependency is introduced:

<app-state> ---depends on---> <ui-action-streams> ---depend on---> <app-state> 

The break this circular dependency, <ui-action-streams> must be created before <app-state>. And because action streams are created before the UI, there is no chance to emit events into them (due to immutable characteristics of EventStreams) unless they are buses/subjects. Thus, buses/subjects seem to be the only option for now..

I you have an implementation with FRP & React without using buses/subjects, I'd gladly look at it and get some inspiration how to do this "better". :-)

I've created (yet another) Flux library that hides the ugly implementation details of buses/subjects and focuses on functions and event streams instead. You can take a look at it: https://github.com/milankinen/ffux

from react-bacon-todomvc.

thanks

from react-bacon-todomvc.