didUpdateWidget sets the form to pristine and untouched about reactive_forms_generator HOT 5 CLOSED

Cool, I'm happy with the verdict. reactive_forms_lbc looks useful, cheers.

from reactive_forms_generator.

Do note that the required validator trims the white space so the value ' ' is indeed invalid, and I did 2 spaces so that it is different to the model and enters the important code in didUpdateWidget.

from reactive_forms_generator.

It reconstructs only if

if (widget.model != oldWidget.model)

So if you are changing the model it means that this is new form so everything will be new

Implement proper object equality with equatable or freezed to have consistent behavior

from reactive_forms_generator.

I managed to change my app to make it work. I will ponder this form becoming pristine on model updates behaviour some more before I close.

I'm building a complex object by listening to formModel.form.valueChanges, and my forms also need to read that complex object, so it listens to it and rebuilds.

It worked in version 0.24, but I think in version 1.0.0, when the form rebuilds, didUpdateWidget is running with a different model (by one character), causing the reconstruction with pristine.

For my solution I don't update the complex object in formModel.form.valueChanges anymore, so the form no longer rebuilds on value change. I do it on button presses, when it is okay to allow the form to be pristine, and also put the current form state that is missing from the complex object, in a separate object so I can get a full picture of the complex object now from 2 different objects.

from reactive_forms_generator.

There is https://pub.dev/packages/reactive_forms_lbc package which could help you to simplify listening

In overall it makes more sense to pass model into form and then operate the using form methods without resupplying the form with new model

from reactive_forms_generator.