Formik - Building React Forms easier

แชร์
ฝัง
  • เผยแพร่เมื่อ 11 พ.ย. 2024

ความคิดเห็น • 35

  • @MonsterlessonsAcademy
    @MonsterlessonsAcademy  2 หลายเดือนก่อน

    WATCH NEXT: React Interview Questions and Answers - Dominate Your Next Interview - th-cam.com/video/yQHr4opz_N0/w-d-xo.htmlsi=51b2XP_84GH3q6oF

  • @predator00071
    @predator00071 ปีที่แล้ว +2

    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!!

  • @truechannel2k24
    @truechannel2k24 2 ปีที่แล้ว +2

    Thank you so much for making stuff in soft a lot easier to understand.

  • @megamind770
    @megamind770 11 หลายเดือนก่อน +1

    You're a life saver!

  • @ibrahimkhurshid4339
    @ibrahimkhurshid4339 2 ปีที่แล้ว +2

    So well explained.

  • @zoki5388
    @zoki5388 2 ปีที่แล้ว +2

    You are creating good content. Could you make video about react tables?

  • @mrpunch_777_
    @mrpunch_777_ ปีที่แล้ว

    Good explanation and straight to the point, content was really helpful . By the way, my company is still using formik.

  • @mazingamal3580
    @mazingamal3580 11 หลายเดือนก่อน

    really thanks u bro , u r amazing .. i think it's better than react hook form and very easy

  • @PraveenKumar-ft2kr
    @PraveenKumar-ft2kr ปีที่แล้ว

    Excellent Video . Thank you :)

  • @zaytungbonn184
    @zaytungbonn184 ปีที่แล้ว

    it was really really good. thanks a lot

  • @KhaledABED-m5j
    @KhaledABED-m5j ปีที่แล้ว

    Very helpful... thank you

  • @waleedsharif618
    @waleedsharif618 2 ปีที่แล้ว +1

    Could you make video about react testing using react testing library + jest ?

  • @mateusgomes1086
    @mateusgomes1086 2 ปีที่แล้ว +5

    Formik is no longer supported since June 2021. Just use react-hook-form instead.

    • @MonsterlessonsAcademy
      @MonsterlessonsAcademy  2 ปีที่แล้ว +2

      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 :)

    • @ThiagoVieira91
      @ThiagoVieira91 ปีที่แล้ว +1

      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.

  • @gubatenkov
    @gubatenkov 2 ปีที่แล้ว +4

    dont use formik on production. You will get +100500 rerenders on each onChange

    • @grenadier4702
      @grenadier4702 2 ปีที่แล้ว

      The thing is not in rerenders but how it affects optimization. Many websites use Formik, so I guess everything's okay with that? :)

    • @MonsterlessonsAcademy
      @MonsterlessonsAcademy  2 ปีที่แล้ว +2

      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.

    • @gubatenkov
      @gubatenkov 2 ปีที่แล้ว +1

      ​@@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?

    • @gubatenkov
      @gubatenkov 2 ปีที่แล้ว

      @@MonsterlessonsAcademy no problem until you have to rewrite the code

    • @grenadier4702
      @grenadier4702 2 ปีที่แล้ว +1

      @@gubatenkov Convenience or bad architecture overall, not the problem of Formik

  • @frozen_tortus
    @frozen_tortus 6 หลายเดือนก่อน

    "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.

  • @shashankpandey8346
    @shashankpandey8346 7 หลายเดือนก่อน

    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?

    • @MonsterlessonsAcademy
      @MonsterlessonsAcademy  7 หลายเดือนก่อน

      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}}