Jed Richards

@cloud-walker The `` API explicitly lets you mutate the Formik state as it passes through the `onChange` handler. What's the technique for doing the same in component-component's `didUpdate`?

@cloud-walker Hmm, maybe I'm misunderstanding. As I understand it one of the use cases for `` was to trigger changes in the form state when a field changes. That is,...

@cloud-walker Yeah exactly. Got it now - thanks! 🙇

I'm using brfs 1.4.1 which pulls in static-module 1.1.3 and still can't get brfs to work happily with ES6/babelify. Using same workaround as others for the moment, `var fs =...

Hmm, yep same here. Isn't the best approach to give an option in the Emmet settings to choose the expand button? Like autocomplete-plus lets you switch between `tab`, `enter` and...

The middleware/api actions in the official real world Redux example uses the `_REQUEST`, `_SUCCESS` and `_FAILURE` pattern. For my part I think this is more idiomatic Redux / best practice...

As well as OS notifications, I'd love the desktop app to reproduce some, or all, of the functionality currently available in the web app `/notifications` inbox. It's cumbersome to manually...

Agree. Redux Form is in the business of accurately modelling a form's state over time, but returning a promise being the only way to signal that a submit handler is...

I feel like there's _almost_ 100% perfect saga support as is (and indeed redux-thunk support, since it suffers from the same issue). I setup my form like so, ```js const...

@Alxandr Your `reduxSagaForm` function sounds interesting, is this something you've published?