JC
In terms of functions that would be run against reads and writes, are you talking about [rules](http://docs.datomic.com/query.html), or more manual functions that receive a query, parse and determine whether or...
@xsc checking in on this
`React.Component#setState` is by its own nature async and goes through batching for efficient UI updates. I'll try to put together a small fiddle to see if I can replicate the...
Here's a fiddle with a contrived example of what we're doing https://jsfiddle.net/acj30a5u/1/, hopefully it helps
If I'm not mistaken, React will do what you're talking about if the event is synthetic (ie. managed by React). Any other kind of event that triggers `setState` will execute...
To be clear, I'm in favor of throwing when dispatching during a dispatch. I think that was a good decision. It's just currently causing problems for us.
Yeah, I think cascading dispatches is a real potential problem and something the flux spec is explicitly against, which is why I'm still pro leaving the throw in there, even...
@jordangarcia any thoughts on the above?
:+1: on this. Early on I was doing some pseudo-type checking on getters using `isGetter`, but decided to drop that approach because I didn't find it reliable enough.
Definitely @jordangarcia. I think this kind of approach is useful in dev, where you don't care about perf. In the future, I actually think Nuclear should automatically turn this (and...