Radio group "A component is changing an uncontrolled input to be controlled."

[borachoidev]

I’m using Mantine’s useForm like this:

const form = useForm({
  initialValues: {
    choice: 'a',
  },
});

useEffect(() => {
  form.setValues({ choice: data.choice });
  form.resetDirty();
}, [data]);

<Radio.Group {...form.getInputProps('choice')}>
  <Stack>
    <Radio value="a" label="A" />
    <Radio disabled={!hasAccess} value="b" label="B" />
    <Radio disabled={!hasAccess} value="c" label="C" />
    <Radio disabled={!hasAccess} value="d" label="D" />
  </Stack>
</Radio.Group>

And I’m getting two console errors:

A component is changing a controlled input to be uncontrolled. This is likely caused by the value changing from a defined to undefined, which should not happen. Decide between using a controlled or uncontrolled input element for the lifetime of the component. More info: https://react.dev/link/controlled-components

This happens on the radio button whose value matches the initial value

A component is changing an uncontrolled input to be controlled. This is likely caused by the value changing from undefined to a defined value, which should not happen. Decide between using a controlled or uncontrolled input element for the lifetime of the component. More info: https://react.dev/link/controlled-components

This happens on the radio button whose value matches the fetched value.

When I try to change the value to “A”, the radio button doesn’t detect the change. If I select another option first and then choose “A” again, it finally works.
I don't know which part is wrong.

my mantine version is 8.1.2.

[rtivital]

Please provide a sandbox with a minimal reproduction

[borachoidev]

@rtivital
here it is.
https://codesandbox.io/p/live/091ff82f-6e44-4dc5-9ba8-44a6ec518e3e

I set “a” as the initial value, then I fetch data and update the form value. After that, selecting “a” doesn’t update the form state. It only updates if I choose a different option first and then select “a” again.

[rtivital]

Thanks for reporting, the issue will be fixed in the next patch