Different controller behaviour in v7.41.0

[bluebill1049]

  Hi guys,

i just stumbled across some weird behaviour with the new version v7.41.0.
It seems like the defaultValue of the controller can no longer be accessed with the field.value property.

in my project, i have a function, which renders my form fields depending on the settings i get from the database:

const ReturnAndRenderSettings = (): ReactNode[] => {
        return availableSettings.map((s) => {
            return (
                <div className={"field"}>
                    <Controller name={s.Name} control={settingsControl}
                                defaultValue={userSettings.find(
                                    us => us.SettingId == s.ID)?.IsEnabled ?? false}
                                render={({field, fieldState}) => (

                                    <Setting name={s.Name}
                                             disabled={inSubmit}
                                             defaultValue={field.value}
                                             onChange={setSettingsValue}/>
                                )}/>
                </div>
            );
        })
    };

As you can see here, i´m searching for the matching setting which i get from the server, and then i get the actual value from the IsEnabled property. As fallback i´m using false.

This code worked fine till v7.41.0 and the result looked like this:

However with the newst version field.value is always undefined.
The result, as expected, looks like this:

It seems like in version <7.41.0 field.value was identical with the controller default value, and since 7.41.0 this is not the case anymore.

I´ve read about the new values and defaultValues things in the new versions but found no connection to the controller, so this makes me wonder if i´m missing something here🤔

Originally posted by @manuelpoelzl in #9613

[sofsscosta]

Second this problem, I have also just encountered this in my repo. Also looking for a solution here

[Moshyfawn]

This fix is in and is going to be included in the next release. No ETA