Jimmy Jia

:+1: This would be really cool to have.

babel-plugin-dev-expression strips warnings, but it's not going to do anything for actual errors. Errors are errors, after all.

warning doesn't log in production, but you need the Babel hook to strip out the calls and messages from production builds entirely.

`babel-plugin-dev-expression`, like I mentioned, but the library should be running that Babel transform, not you.

That would be all sorts of amazing. Re-build Flux with mutable stores/&c. on top of Redux? Is the core of this essentially a competing model to redux-thunk/redux-saga for handling side...

I haven't tried, but it seems like getting something like data sources to work in a Redux paradigm would be tricky – or at least very different.

Commenting from the sidelines a bit, but having like 3 or 4 different ways to do everything really was the weirdest part of the Alt API.

Well, @goatslacker can correct me, but I don't think that's true. Alt is most likely the best-in-class solution for an imperative approach to the Flux architecture, as opposed to the...

I have essentially a copy of the behavior from Marty (rip) in #400, where each fetch operation is assigned an `id`. That sort of handles both this and #483, in...

To be more concrete, the pattern that I'm finding tricky/annoying to implement right now looks like: - User is on `/foo` - User does SPA navigation, we call `history.pushState` to...