Pristine and dirty shouldn't change between wizard pages.

Are you submitting a bug report or a feature request?

Bug report

What is the current behavior?

1. Fill first and last name (pristine should change to false)
2. Click next
3. pristine back to true
4. Back to previous page
5. pristine is still true

What is the expected behavior?

pristine and dirty shouldn’t change between wizard pages.

or:

There should be other way, to check state of fields that are not currently in the DOM.

Sandbox Link

https://codesandbox.io/s/wizard-field-state-gfevw?file=/Wizard.js

What’s your environment?

n/a

Other information

I have multi-paged form (without validate on each page) and I want to block submitButton, when nothing has changed.

[jeremy8883]

We ran into a similar situation, where we had some fields inside an accordion. When an accordion item is closed, its child components become unmounted, and therefore many of the Field components in the form become unmounted.

Our app is required to automatically save the form when we leave the page, but only if the form is dirty. To do this, we check the dirty state of the form state. Because the dirty state was getting reset back to false when an accordion item was getting closed, the save was not occurring in these situations when it should have.

Are there any recommendations to work around this issue? The best idea I could come up with was to track the dirty state ourselves. Which is unideal, because now we have two versions of dirty, and we need to ensure that future developers don’t use the wrong value.

[erikras]

The way the Wizard is implemented it is keeping each page as a separate form, and the combining only the values in the parent component. This solves many problems like forcing validation when hitting “Next”, only marking the fields on the page as touched when validation halts submit, etc.

You could potentially raise the <Form> component up into the parent and then do some sort of conditional validation for each page, but then you’ve got a whole myriad of other problems to deal with.

do you think there’s any chance that something is done about this in the library itself?

No.