Hi @BinaryMuse,

I lost you on IRC yesterday, so I'm putting the same questions up here :):

1. if views are only meant to trigger actions (which you point on the docs), wouldn't it be better
   if only actions would be available in views? This would force the developer to get off the comfort
   zone and realise that it isn't the intended way and it would also make the syntax cleaner.
2. what's the difference between FluxMixin and FluxChildMixin? Or, in other words, why does FluxMixin tell the child context if a child view is intended to use FluxChildMixin and get flux using this.getFlux()?
3. have you thought about namespacing actions? I know that they're supposed to have a unique constant that tells them apart (e.g., ADD_URL), however I have a feeling that this approach may eventually lead to less clarity on which actions the view depends on.

Thanks in advance for your time,
Darío