Bro, His way of teaching is very didactic. And your video is very short, making it easy to follow. You separated the basics in one video, and more features in others, making it really cool to watch. Thank you!!
You are totally right. But there are still lots of companies that use it in production and it is quite stable. And we get new libs that do the same thing too often for my taste :)
Wow really!? You just made my day. Formik has the same base concepts of Redux-Form, which I'll hate until my death bed. Gonna get this lib out of our project today immediately.
Formik does no magic. If you write plain form handling you will also get rerender every time. Which is totally fine because it allows you to show validation/etc. If you have other cases you might write it differently. I don't really see a problem.
"Best posible way", difficult to take you seriously with statements like that backed by 0 evidence. I was hopping you where going to compare it with some other similar form management solutions, but I was left disappointed. If I where you I would restrain myself from polarizing statements like that esspecially if you don't back them up.
I really am confused. {formik.errors.email && formik.touched.email && formik.errors.email} In this line, I need to write formik.errors.email twice? It seemed to work touched & error, but not other way around. And is there any hidden catch in touched & errors too?
You check that you have an error for email and that the field is touched - then you render email error {errors.email && touched.email && {errors.email}}
WATCH NEXT: React Interview Questions and Answers - Dominate Your Next Interview - ua-cam.com/video/yQHr4opz_N0/v-deo.htmlsi=51b2XP_84GH3q6oF
Bro, His way of teaching is very didactic. And your video is very short, making it easy to follow. You separated the basics in one video, and more features in others, making it really cool to watch. Thank you!!
Glad it was helpful!
Thank you so much for making stuff in soft a lot easier to understand.
So well explained.
Thank you!
You're a life saver!
Thank you!
Good explanation and straight to the point, content was really helpful . By the way, my company is still using formik.
As a lot of other companies
Excellent Video . Thank you :)
You are welcome!
it was really really good. thanks a lot
Most welcome 😊
You are creating good content. Could you make video about react tables?
Thank you for the idea. I will add it to the list
really thanks u bro , u r amazing .. i think it's better than react hook form and very easy
Most welcome 😊
Could you make video about react testing using react testing library + jest ?
I will add it to the list of ideas for future videos.
Very helpful... thank you
Glad it was helpful!
do you still recommend using this today?
It still works just fine but react hook form is much more popular solution nowadays.
@ 🙏🏽
Formik is no longer supported since June 2021. Just use react-hook-form instead.
You are totally right. But there are still lots of companies that use it in production and it is quite stable. And we get new libs that do the same thing too often for my taste :)
Wow really!? You just made my day. Formik has the same base concepts of Redux-Form, which I'll hate until my death bed.
Gonna get this lib out of our project today immediately.
dont use formik on production. You will get +100500 rerenders on each onChange
The thing is not in rerenders but how it affects optimization. Many websites use Formik, so I guess everything's okay with that? :)
Formik does no magic. If you write plain form handling you will also get rerender every time. Which is totally fine because it allows you to show validation/etc. If you have other cases you might write it differently. I don't really see a problem.
@@grenadier4702 I know a lot of teams that have and are now rewriting all their site forms from Formik to Hook-form. Any idea why they did this?
@@MonsterlessonsAcademy no problem until you have to rewrite the code
@@tenkkov Convenience or bad architecture overall, not the problem of Formik
"Best posible way", difficult to take you seriously with statements like that backed by 0 evidence. I was hopping you where going to compare it with some other similar form management solutions, but I was left disappointed. If I where you I would restrain myself from polarizing statements like that esspecially if you don't back them up.
I really am confused.
{formik.errors.email && formik.touched.email && formik.errors.email}
In this line, I need to write formik.errors.email twice?
It seemed to work touched & error, but not other way around.
And is there any hidden catch in touched & errors too?
You check that you have an error for email and that the field is touched - then you render email error
{errors.email && touched.email && {errors.email}}