Formik material-ui doesn't link to react state in component

[tgrrr]

Formik material-ui doesn't link to react state in component

[cliedeman]

Ah I think I get it now. The question could be why do I explicitly exclude these fields

export interface CheckboxProps
  extends FieldProps,
    Omit<
      MuiCheckboxProps,
      'form' | 'checked' | 'defaultChecked' | 'name' | 'onChange' | 'value'
    > {}

The reason is that I want exactly one place for state to be stored. That being said modifying state outside of formik happen often enough.

Would this pattern work for you?
https://codesandbox.io/s/goofy-jepsen-2s4f4

Otherwise you can always create your own special case field.

Ciaran

[cliedeman]

Hi @tgrrr, Thanks for the example but I am struggling to see where it is breaking.

Is there a specific reason you have state outside of formik?

const [toggle, setToggle] = useState(false); looks very strange to me

[tgrrr]

I'm not sure why people wouldn't want control to get + set state outside of Formik itself.

We don't just interact with form components when we hit a submit button.

Some components interact with one another, and other components. Eg. Setting the value on a checkbox hides another component.

The example you copied is just managing state with hooks. It can be swapped out for setState, redux, or any other state management.

The point is that there's freedom to interact with react's state in Formik. Why wouldn't this also exist in Formik-Material?

[tgrrr]

Yes, I feel like that is exactly the question, thanks.

Would this pattern work for you?
Which pattern do you mean?

[tgrrr]

Why was this closed @cliedeman?

[cliedeman]

Because it’s working as intended. This library delegates all state management to formik.