Allow for updating form fields that are not yet rendered about final-form-calculate

[erikras]

You can now update non-registered fields in [email protected].

[greeksolid]

@alexjsdev I had similar requirements with you (change value of a related field that is rendered on another step of a wizard form). An ugly way I found to get around this problem is to declare a field with the same name as the one I wanted to change, in the container component of the wizard so final-form-calculate can see it as a registered field and change its value.

example : <Field name="fieldYouWantToChange" component={() => null} />

I have not yet noticed any problems with this except ugly hacky code.

[617dev]

@erikras I don't mean to bug you, but i'd love to help if you'd accept a PR for this, but could you point me in the right direction? I really need this functionality...

If i'm not taking the right approach, what am I missing? is there a better way to accomplish what i need to do?

[erikras]

It can also be done in bulk with something like this. final-form/final-form#102 (comment)

However, having thought about why I chose to not allow changes to non-registered fields, I cannot defend the decision. It makes the library less flexible. So I'm going to reverse that decision.