I'll at least echo some of what has already been said. React Hook Form has a lot of additional features that this new hook wont cover - so I'll be sticking with that. While I don't consider it to be "magic" (clearly the tag now has a context associated with it), it still feels like a little bit of "sleight of hand-ish". In RHF you explicitly have to use their context component to be able to refer to the enclosing form in child components. So there is some level of "mystery" with this new React hook. I can see that it may help isolate naming conflicts but just how many places in a component containing form do you really need a "pending" state? If you are writing tightly-purposed components... maybe once in that component? So I think naming clashes are going to be rare. Also, as pointed out, there's not much difference in the amount of code being written and the benefits come more to those using React in a SSR environment - especially where FormData is prominent.
The input ref wasn't really needed in the previous implementation anyway, since you automatically get refs for named inputs within forms in the FormEvent given in onSubmit. You can have a near-identical implementation for onSubmit by doing `const data = new FormData(e.currentTarget)`.
Is passing a callback to the "action" something that also comes with the new React version, or is it something that exists already? If it's available in the current version of React, why aren't we using it instead of onSubmit?
These all “new concepts” from react / vercel / nextjs team is taken from Remix. So you can just use Remix and have all the goodies stable (in general).
it's nice for learning cutting edge, but would never use any alpha/beta in a production product. React Hook Form, is meant to be used in production out of the box
Like William said, in prod I’d stick to RHF, but once this goes stable, I’d be more inclined to use this as it’s built in and requires less package overhead in my bundles.
Nice video. I prefer the first method though. At times, there may be some logic to be done like show a toast and just having one loading state that's your single source of truth seems easier and more straightforward.
if only this wasn't formdata I'd be excited. But I really don't like working with that. I mean sure it's native and it technically makes sense, but json is just so much nicer most of the time. Only time I use FormData is with file upload, and I always hate every minute of it.
geez React gets overloaded with hooks that are really just workarounds for basic stuff. Instead of clean code we get a bunch of functions that have some "magic" going on under the hood. Maaan as I get older, I tend to dislike React very much.
The first minute of this video reminds me of how important consistent dog-fooding of your own [company's] application is. You can't just develop on your local machine, and under/for your own circumstances, technical and other. You must incorporate a realistic range of devices, network/speed ranges, screen sizes, etc. into your dev iterations, AND frequently use your app out in the wld.
Personally I feel this is just unecessary, maybe for really complex multistep forms like a visa application software I can understand but to me there is no way that your initial solution or a oneline debounce function is more complicated than implementing all of this especially compared to your complaints being "an extra loading variable??, difficult getting names correctly??" like what?, I'm happy for the vid though
1. I'll pretend that I managed to follow everything you said. 2. It is not the first time that you are uploading content of hooks with an experimental status. And what if the experiment will fail..? I find this urgency for being the first one talking about it, at least...... Questionable.
You don't need to buy anything. There is enough free material present on the internet to learn from. I am a self taught developer and learnt everything for free.
React Simplified Course: reactsimplified.com/?Udtt6H5CE
You can also use use-form-hook
Please can you make a review of the exchange-router module on npm
I'll at least echo some of what has already been said. React Hook Form has a lot of additional features that this new hook wont cover - so I'll be sticking with that. While I don't consider it to be "magic" (clearly the tag now has a context associated with it), it still feels like a little bit of "sleight of hand-ish". In RHF you explicitly have to use their context component to be able to refer to the enclosing form in child components. So there is some level of "mystery" with this new React hook. I can see that it may help isolate naming conflicts but just how many places in a component containing form do you really need a "pending" state? If you are writing tightly-purposed components... maybe once in that component? So I think naming clashes are going to be rare.
Also, as pointed out, there's not much difference in the amount of code being written and the benefits come more to those using React in a SSR environment - especially where FormData is prominent.
Yeah I instantly thought reacr-hook-form too. I guess eventually it may be redundant
The input ref wasn't really needed in the previous implementation anyway, since you automatically get refs for named inputs within forms in the FormEvent given in onSubmit. You can have a near-identical implementation for onSubmit by doing `const data = new FormData(e.currentTarget)`.
Nice one
I'm using react-hook-form for this and it gives additional benefits, such as schema validation with various libs (Yup, Zod, etc.)
Is passing a callback to the "action" something that also comes with the new React version, or is it something that exists already?
If it's available in the current version of React, why aren't we using it instead of onSubmit?
Does anyone have a guess on when these new hooks will be released as stable? Seems like they should have existed long ago.
Seems like it will take some more time because this is a fairly recent feature that is a complement to Server Actions (SA are still in alpha)
Always check their documentation
I don't know bro, maybe check their roadmap.
@@sicfxmusic ok bro
These all “new concepts” from react / vercel / nextjs team is taken from Remix. So you can just use Remix and have all the goodies stable (in general).
that's exactly how remix run are handling forms, I was surprised how no one in the comment or even you Kyle did monition it.
would you use this over react hook form?
I was wondering the same
it's nice for learning cutting edge, but would never use any alpha/beta in a production product. React Hook Form, is meant to be used in production out of the box
Like William said, in prod I’d stick to RHF, but once this goes stable, I’d be more inclined to use this as it’s built in and requires less package overhead in my bundles.
react solves problems that react has created in the first place
Mantine’s useform + zod feels light years ahead tho
Kyle, pls bring out a full length react course on youtube 🙏🏻
Nice video. I prefer the first method though. At times, there may be some logic to be done like show a toast and just having one loading state that's your single source of truth seems easier and more straightforward.
This seems pretty similar to AntD implementation of Form but, it's good to have this out of the box.
if only this wasn't formdata I'd be excited. But I really don't like working with that. I mean sure it's native and it technically makes sense, but json is just so much nicer most of the time. Only time I use FormData is with file upload, and I always hate every minute of it.
your course is best for React Hooks , Appriciated
Nice. It was just dealing with this bug in my application so seeing this being addressed with a new hook, it’s right up my alley. Thank you.
Thanks a lot for this tutorial.
geez React gets overloaded with hooks that are really just workarounds for basic stuff. Instead of clean code we get a bunch of functions that have some "magic" going on under the hood. Maaan as I get older, I tend to dislike React very much.
Same
thats exactly what happens
I agree. I’m not doing my next project in react.
very great tutorial, thanks a lot ❤
When will your NextJS course be released on your course platform? :D
This is truly epic! The php feel
Great tutorial, can see react is getting a PHP feel
The only channel whose speed I'm slowing down.
same here, speed 0.75 for Kyle
BTW, does the 'data' of 'FormData' type has a method to allow us to set it blank right after submit?
Hey Kyle great vid, listen how can I use env vars with vite + react?
What about useNavigation hook? How is it different from this hook?
i love this react hook!
Thank you🎉
would this affect Next.js Server Action?
Awesome!😍
I feel using state is easier, and creating a custom form component😀!
Still too many line codes. If It was related tô the structure of the like a paramater telling to "wait" the onclick function to happen.
why i love nextjs ❤❤❤❤
Awesome!
The first minute of this video reminds me of how important consistent dog-fooding of your own [company's] application is.
You can't just develop on your local machine, and under/for your own circumstances, technical and other.
You must incorporate a realistic range of devices, network/speed ranges, screen sizes, etc. into your dev iterations, AND frequently use your app out in the wld.
This is pretty much how useFetch works on Nuxt 3, except it doesn't require tying specifically to a form.
Why this wasn’t the behavior from day 1, idk. But this is a beautiful addition.
thanks guruji :)
Neat, but I will stick to disabling the button though
Hi Kyle!
I need crud app with json server lesssons!
Please tech it and upload lesson
Why don't you have any angular tutorials?
Use react-hook-forms is the best
isnt this even more complicated than the original isLoading
4:20 lost me on creating a new and unecessary abstraction just to provide context to the tool, doesn't feel like a good syntax
GoodJob!
This can't happen when using RemoteData in PureScript
Personally I feel this is just unecessary, maybe for really complex multistep forms like a visa application software I can understand but to me there is no way that your initial solution or a oneline debounce function is more complicated than implementing all of this especially compared to your complaints being "an extra loading variable??, difficult getting names correctly??" like what?, I'm happy for the vid though
Data Driven Forms is still a way to go for me. This is really limited. :/
1. I'll pretend that I managed to follow everything you said.
2. It is not the first time that you are uploading content of hooks with an experimental status.
And what if the experiment will fail..?
I find this urgency for being the first one talking about it, at least......
Questionable.
I always turned my submit button into a spinner until I get a reply from the api
I do the same
Bro I am From Pakistan, For me Your courses are too Expensive 🥺🥺
What would be a good usd cost for Pakistan viewers. Impressive you know English.
You don't need to buy anything. There is enough free material present on the internet to learn from. I am a self taught developer and learnt everything for free.
I wasn't subscribed... sorry bro, love your channel
Imagine not using Svelte.
The fact that this is an experimental feature was not put into the title or thumbnail, giving this a thumb down.
I am so far away.
not that much helpful. Give us the best way of handling form data without pre rendering
You should have started the video by saying this is an experimental hook! 🙄
Meh, the old way is easier.
I just started react and i don't know what projects to make ..... can anyone help me out
Can we finally stop using todo stuff for react tutorials?