Erik Aybar

I'm trying to do something similar and running into confusion. It seems like this should be possible since according to https://github.com/final-form/final-form#mutator-args-any-state-mutablestate-tools-tools--any > A mutator function that takes some arguments, the...

@tadger I'm recently back to asking this question for now a different use case (see https://github.com/final-form/final-form/issues/154#issuecomment-479201028) Did you ever come across a solution for mutating `formState.errors`?

@henus we are currently facing this same need. Have you come across a solution here? Our use case is roughly: * We have a `react-final-form` form embedded on a legacy...

Hi @drcmda! I just came across `react-contextual` and found it compelling. Two thoughts that come to mind for me are: **1. Update README to use actual code snippet examples rather...

Another thought that comes to mind is that I would typically define the majority of my state/actions somewhere at the top level "App" layer. I can envision some form of...

Sounds good @drcmda. I'll see if I can get some time to put that README focused PR together this week. --- On the concept of `MultiProvider`: > why not merging...

How about an image?! 

After looking at codeception and their REST module I'm leaning that way in favor of behat

I think as soon as we have the basic "Testing ORM Relationships" tests properly defined, up, and running we can close this. Then we can move to using a bit...