Top 6 React Hook Mistakes Beginners Make
HTML-код
- Опубликовано: 3 июл 2024
- FREE React Hooks Simplified Course: courses.webdevsimplified.com/...
📚 Materials/References:
FREE React Hooks Simplified Course: courses.webdevsimplified.com/...
Reference vs Value Video: • Reference Vs Value In ...
Reference vs Value Article: blog.webdevsimplified.com/202...
🌎 Find Me Here:
My Blog: blog.webdevsimplified.com
My Courses: courses.webdevsimplified.com
Patreon: / webdevsimplified
Twitter: / devsimplified
Discord: / discord
GitHub: github.com/WebDevSimplified
CodePen: codepen.io/WebDevSimplified
⏱️ Timestamps:
00:00 - Introduction
00:39 - Using state when you don’t need it
02:57 - Not using the function version of useState
06:44 - State does not update immediately
08:25 - Unnecessary useEffects
12:40 - Referential equality mistakes
16:55 - Not aborting fetch requests
#WebDevelopment #WDS #JavaScript
React's own docs explicitly recommend using state-controlled inputs over refs whenever possible. It refers to the ref method as "quick and dirty" because it lets the DOM handle tracking the value instead of React, which can sometimes cause unexpected behavior when React renders its virtual DOM. So... yeah. I think for forms, especially large ones, it's better to keep track of values in a single state object with key-value pairs. That does mean it'll re-render whenever a value changes, but since React only manipulates the DOM for the one input that's changed, it's not a big deal; and it allows React to have more control over, and more understanding of, the inputs, for optimizations.
The main issue with using local variables instead of useEffect for composite values is future-proofing: when you add more state to the component, those variables will be re-evaluated on every re-render even if they don't need to be. In such cases, I think useMemo is the optimal solution; in fact, it's why useMemo exists! (And I believe recomputing a memoized variable doesn't trigger a re-render the way setting state does, though I couldn't find anything definitive about that.) But you are right that in some cases, you don't need to listen for changes at all, since you can just use the new value at the same time as you're setting it on the state.
I think useRef should be used for forms, you don't want component re-rendering on every key stroke just for a form, but if you was using a search/filter input where you are filtering on the users key stroke then you would need to useState and make it a controlled component.
@@SahraClayton It only re-rendered the input DOM tho? Instead of the whole form if I understand it correctly. I don't think it's a big deal.
@@chonmon yes, not to mention you'll always want to have some kinda validation on the form.
@@chonmon it's not a big deal but if you can avoid any components from rerendering no matter how small is just a bonus. Also it's less syntax in that component, which looks nicer
@@SahraClayton then you can opt for other event like submit or blur to minimize re-render. Although useRef is a fine solution since there’s no re-render, using it with forms that have many fields or require validation will give you a hard time managing these fields’ value and their behaviors
Golden tips! Love content like that with different case scenarios and clear explanation! I have learnt so much! Thanks for sharing!
well this is what I am looking for ages. THANKS KYLE, you made my day, now I can revise my old code at a higher level
Hands down, what a perfect rhetoric - watched it with great pleasure - thanks
This was soo helpful. I had a beginner project, just for fun and I almost made all of the mistakes. I just fixed my code, and it looks much better now. Thank you
one of the best React tips I ever learn on RUclips. Thank you so much
Fantastic! I’m just learning react and you’ve explained the funky behaviour I’ve been getting with useState perfectly. Thanks for taking the time to make these videos 😊
Why are you excited to watch while the other crying are u happy
It was worth to watch, I learned pretty valuable things especially the fetch abort, it's golden, thank you!
For handling form why not simply grab the input values from the onSubmit event? No need for state or refs.
Yes that is what I usually do.
const formData = new FormData(e.currentTarget)
and then
const [username, password] = [formData.get("username").toString(), formData.get("password").toString()];
looks cleaner to me than using refs or state there
well I still use state for input validation though
Hey Kyle,
This is really very helpful for me.
Tomorrow I have a task to complete in my office.
I was worried about how to do that.
but, this video gave me a clear idea about that.
Thanks a lot. Keep going, bro.
Loves from Sri Lanka ❤
This worked incredibly well! I can finally play it thanks
amazing video for react beginners. :) Thank you. Looking forward for more react mistakes that beginners and more advanced devs make
This was really straight to the point and very helpful. Thank you Kyle! :)
last one just perfect! thanks!
This was a great video and helped me solve an issue i had with my hook, namely having multiple states update with an action needed once they were both updated. it took a while to wrap my brain around it, but this video really helped give me the vision. love your videos and that you go super in depth (in the longer ones). probably the best coding tutorials on youtube. if i ever get my web dev dream job, i will be getting you a few coffees/beers.
Thank you Kyle!
Excellent explanation on state setter usage
Thanks for video Kyle
I really appreciate your explanations. Top-notch!.
Amazing explanation! Many thanks
This is the single most useful video I've seen since I started React coding
I really appreciate this video!! 🙌
Amazing! You make great content. I especially like your youtube shorts
Really useful one. Please keep on making great informative videos like this. You're the best!
Awesome explanation ❤
Amazing video, thx a lot!
It was amazing man. Thanks a lot🔥🔥
thank you for this great quality content
Excellent video, thank you very much.😊
Thank you so much, as a beginner you helped me a lot
best explanation of useMemo out here👏🏽
Great video ! Well explained ! Thank you, I'm modifying my code right now...
This is really helpful ❤️
A good thing to point out about the first mistake is that a good UX informs the user if the field has any errors while they are typing; in this case, this is not possible. Better to stick with states, but it is a nice thing to know.
Simple and brilliant
00:45 tag stores fields value
excellent ! Big thanks
Thanks. I didn't knew these.
Very clear video, I just switched to Typescript for last major project, took a bit of effort initially but rewards are great, the build step catches a good few errors very early. I think not using TS could be added to your list. I expect many that haven't given it sufficient time will disagree.
I spent hours on my degree final project sorting out errors that js didn't pick up until I tried to run a piece of code with an error in. Switched to TS and it's a million times better and Id also say I've learnt a lot more too
You just prevented some lay offs, great job.
Great! Thanks from Brasil!!!
super informative and helpful
Nice tip last one.Thanks
For the first case you don’t need state or refs the onSubmit function has access to all the input fields via the event parameter
You really deserve thumbs up from me. Good Job. 👍
You are AMAZING ... Kyle 💐
Good tips , thanks for sharing
Good work Kyle 😉
Thanks a lot. These are very important and useful knowledges.
Well done sir, excellent video. Thank you for your hard work.
I even express with words how much this video has helped me. I got answers to lot of my questions. Thanks Kyle💥
great tutorial, I learned something new today. Thanks :)
The number of useEffect gotchas and permutations are just never ending. I have such a love hate relationship with this hook.
You and me both
I have a relation of pure hate with that hook
that just makes so much sense!!!! thank you for bring the good code
Really good video, very informative and explaining in a clear way.
It's very helpful for React beginner like me! Thank you for your videos :)
this is super helpful
some of the senior developers in a company I worked for used to not approve my PRs asking for me to not use useRef to the store any state in react component. It is nice to see someone explaining why not every state needs to be rerendering the component on every data update.
Great video dude thanks :)
Many thanks! Good luck with your channel! Greetings from Kyiv!))
this video is all react people need, thanks a lot.
I'm thankful I found Svelte and don't have to deal with this complexity. Svelte makes everything so much intuitive. Like yes, there are still some special cases and implementations where you require some special syntax, but for the most part it's just writing regular JS without having to think what wrapper you need.
Most valuable React tips I have learnt regarding some bad code practices I have been applying in React. Thanks for this very comprehensive video with lots of valuable information covered in just over 20mins.
was great like always
Great video. I don't know what more can i say. Cheers!
Very good, on point, thx
Thank youuuu very much
very simple and very useful!
Thank you for share.
that was helpful thank you
Man, using setCount( (count)=>{count + 1} ), it's the greatest way how to handle this real react problem! That's was extremely beneficial for me !!!!! Thank you!
i love react and i love this youtube channel, hi from indonesia
Usefull for beginner like me, thanks 🎉
Last tip was really important ❤
Thanks Kyle
Interesting video Kyle! I noticed I do make a few of these mistakes myself. I think the problem is that us developers can be a bit "lazy" learning new frameworks. I understand how the useState and useEffect hooks work and I never took the time to learn about useRef and useMemo for example.
totally!
You'll use it once you handle big data and use expensive functions that can block the main thread
Well I this case the "lazy" one is the video author. Recommending using refs over state on 1.34M subscribers is a crime.
Thank you
Hey Kyle! Thanks a lot for your awesome videos! Have you tackled about using normal function and arrow function in react js? You seem to use both but I'm not sure what your criteria is. Hope you make a video about it! Thanks!!
that useMemo trick... was lovely
Learning so much 🎉
Thanks, A lot👍
Really helpful
wonderful video.
good explanation !!!, my problem can be solved, thank you very much..
thank you
Thanks
This video rocked my world. Had quite a REACTion to it.
thank you sir what was informative
Subbed for that beautiful Jackson guitar
Using refs instead of state does not seem right in this scenario. First of all, such a render does not create any overhead since behind the scenes react will do equivalent of what you have done with refs. Besides, these code will probably be improved with validators etc. which will result going back to state version
Sus lan
You're correct. React has always preferred controlled components (react handles input value) over uncontrolled components (DOM handles input value). This is second time I see Kyle making this counter-argument to use refs, which I think is incorrect.
This is really debatable, as the scenario Kyle mentioned is that, all the inputs are only used upon form submission. For experienced React developers, we have always been using controlled components and get really used to it, so we are very unlikely to use Kyle's uncontrolled ways in any circumstance.
@@ACMonemanband True. Refs are mentioned in the "Escape hatches" section in the new react docs, which for me intuitively tells that refs are used as secondary option when first option of controlled components doesn't work.
@@ACMonemanband These days I usually just use react-hook-form and don't worry if something is controlled or uncontrolled in a most forms. The fact is that for more complex forms that might compute a lot of stuff, uncontrolled form inputs are better because they won't re-render the whole form on each input change. If you need to do any active validation, you'll probably have to go for controlled forms because you'll have to react to form changes all the time and not just on submit, but in cases where you just need to validate on submit, you probably want to go for uncontrolled inputs.
Only reason I dislike his input ref example is because you'll rarely only work with two field forms in the real world and you'll most likely have multiple (more complex) forms in your app. At that point, just reach for something like react-hook-form and never worry about building forms in React.
Awesome!!
best tips ever. i also was not using functional way of setting state
Useful video❤️
You really have a talent for education my man. Whenever I'm not understanding something in web dev now I just search for web dev simplified and boom there's always a video on it. Thank you! These were really good tips for those of us just getting into front end :)
Wonderful.
thanks
Awesome!
15:45 in that case instead of useMemo we can directly use in the dependency array person.name and person.age and it will not cause rendering when you change the dark mode checkbox
It does work as the same as before in case of email and password, but we use usestate , value and onchange to create Controlled components. Uncontrolled components with refs are fine if your form is incredibly simple regarding UI feedback. However, controlled input fields are the way to go if you need more features in your forms.
so helpful