Maybe it's my lack of understanding but I don't understand why people create libraries that have nothing to offer. I don't understand what formik has to offer more than the native functionality of a browser. With all due respect.
Obviously you didn't had to deal with a lot of complicated forms in your life.
After you create all that by hand you can go back and look formik in depth. Only after you will appreciate that someone took the time to create it.
I don't agree to "formik have nothing to offer". Because formik handles the low-level details for us like we no need to worry about handleBlur, handleFocus and handleChange of fields and also we don't need to create error states, etc. So I prefer it but if you like to work with native functionality then its good, it is totally your choice 🤗
Maybe it's my lack of understanding but I don't understand why people create libraries that have nothing to offer. I don't understand what formik has to offer more than the native functionality of a browser. With all due respect.
Obviously you didn't had to deal with a lot of complicated forms in your life.
After you create all that by hand you can go back and look formik in depth. Only after you will appreciate that someone took the time to create it.
I don't agree to "formik have nothing to offer". Because formik handles the low-level details for us like we no need to worry about handleBlur, handleFocus and handleChange of fields and also we don't need to create error states, etc. So I prefer it but if you like to work with native functionality then its good, it is totally your choice 🤗
I agree, it's a matter of choice. Well said! =)
Formik allows nested values, e.g. user.email, to be easily used in forms.
React does not allow this with useState.