Overriding DefaultValues if form is dirty

Describe the bug When using register to provide DefaultValues to an input, it’s possible that the input component will be removed from the virtual DOM and eventually re-added. Upon re-rendering, register will initialize the input as the DefaultValue, even if the form state has been changed (dirty)

Expected behavior register could be able to use the most recent form state, instead of reverting to DefaultValues.

[bluebill1049]

@marracheco this is how we building wizzard form at work

const { register, handleSubmit, errors, setValue, watch } = useForm({ submitFocusError: false });

const onSubmit = step => data => {
    actions.updateCalculatorDataAction(data);
    actions.updateCalculatorStepsAction({
      [step]: true,
      currentStep: currentStep + 1,
    });
  };

const commonProps = { onSubmit, register, handleSubmit, calculatorData, errors, setValue, 
watch };

const section = () => {
    switch (currentStep) {
      case 0:
        return <BorrowingPowerCalculatorLoan {...commonProps} />;
      case 1:
        return <BorrowingPowerCalculatorIncome {...commonProps} />;
      case 2:
        return <BorrowingPowerCalculatorExpenses {...commonProps} />;
      case 3:
        return <CalculatorDemoPage4 {...commonProps} />;
      default:
        return <BorrowingPowerCalculatorLoan {...commonProps} />;
    }
  };

  return (
    <>
      {section()}
    </>
  );

Each page renders itself and during submission, it will update the data in the store.

[bluebill1049]

@marracheco would you like to send a PR for your Wizzard example? we can have it under example folder. (keep it simple so devs can pick up the idea)