A form can render client side and still post to a server action (like in this vid), which means you can use any front end / hooks you're used to using, including any state, as long as each form field has a "name" attribute
Great tutorial, I like server action, it makes sense to dealing with form this way, from now on no client side dependencies(useState, useEffect) are required, everything is done in server side, so cool, thank you 🙏
I implemented a form using zod validation and server actions that can accomplish this revalidation after each user interaction (including input value changes). If you want to know more about tell me
Are server actions something you're going to start using? 🤔
Forms are not that simple these days, state is needed almost each time i use forms. So there's no plan to use server actions yet
A form can render client side and still post to a server action (like in this vid), which means you can use any front end / hooks you're used to using, including any state, as long as each form field has a "name" attribute
* as long as each form field you want to post to the server action has a "name" attribute
I plan to start using it
Great tutorial, I like server action, it makes sense to dealing with form this way, from now on no client side dependencies(useState, useEffect) are required, everything is done in server side, so cool, thank you 🙏
Thanks for the vid! Great Job!
Hi, what is the main advantage of using a hook, instead of calling just the server action in the form, ex ?
I implemented a form using zod validation and server actions that can accomplish this revalidation after each user interaction (including input value changes). If you want to know more about tell me
Please share!
+1
0:22 Why do we need server action.? what do you mean by creating seperate API route.?
I'll do a video response to answer this question :)
ill honestly just stick to just creating APIs, this is not scalable at all