Elaboration on new formState.isReady field

[HasanMothaffar]

RHF's latest release (7.56.0) introduces a new field to the formState object called isReady.

In the docs, it is described as Set to true when formState subscription setup is ready., followed by this example:

const {
 setValue,
 formState: { isReady }
} = useForm();

useEffect(() => isReady && setValue('test', 'data'), [isReady])

But I'm curious about the situations in which the formState subscription isn't ready, and how this affects reading/setting form values. Is there a link in the docs where I can read more about this topic?

For example, if I have the same code as above but without checking for the isReady field, what will the behavior be? Will the value be set successfully or will it produce an error. I sometimes use this pattern to update form values in a useEffect after fetching data from backend or doing some calculations.

(By the way, thank you for this awesome library :))

[HasanMothaffar]

@bluebill1049

[bluebill1049]

When you try to execute setValue at the child component, and parent level useForm sub is not ready.

[evgeniyworkbel]

When you try to execute setValue at the child component, and parent level useForm sub is not ready.

it should be reflected in docs within example

[bluebill1049]

feel free to send a pr

[HasanMothaffar]

Thank you for your response bluebill1049. There are some points that are still unclear to me:

• What specifically happens if I try to execute setValue at the child component and the parent level useForm is not ready?
• Is this related only to when using FormProvider?
• Does useForm do some async stuff internally that we have to wait for in child component?

I think it might be better if one of the maintainers updated the docs.