Тэги:
#react-hook-form #zod #react #dynamic_formКомментарии:
This is great, but what if the form has over 20 fields, I would need to create a copy of it for every version, is there a more 'versatile' way of achieving this? Maybe when setting the definition of a type in the schema, can I co-require a field, instead of creating different possible versions of it? I'm new to zod as you can tell...
ОтветитьClean !😀... Thanks
Ответитьthank you for help ,you are great teacher❤
ОтветитьThank you very much Sir. I learned a lot. I applied this to checkout page where checkbox is biling address is same with shipping address or not. Thank you very much
ОтветитьThank you, Austin. Your tutorial is very clear and helpful.
ОтветитьWhy you stopped making videos? Your videos are so helpful!
ОтветитьAppreciate the content Austin, subbed and liked! Hope you can continue to create more videos like this
Ответитьits a great tutorial Austin, however I strongly feel you must have adopted some design library as the implementation of Tailwind CSS made this look so clumsy and not on the point to what the video trying to convey. I mostly prefer MUI or Chakra UI for simple and elegant design of forms.
ОтветитьAmazing! Thank you for the content!
ОтветитьThis is a great content, well done. Could you create a slightly complex examle. Lets say there is a drop down and first validation rule is that an option must be selected, it can not be null which is a first option. Depending on a selection different fields are displayed according to some logic. If for example email is selected from the drop down additional email field is displayed and it must be valid email. If telephone is selected then it must be valid phone number etc. I am curious to know how will zod schema look in that case because we have default null state for the drop down and in the case we have more drop downs with different "branching". Thank you.
ОтветитьGreat tutorial!! Your videos are really helpful while I'm learning to use Zod :)
Ответить