Top 6 React Hook Mistakes Beginners Make
VloĆŸit
- Äas pĆidĂĄn 7. 06. 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
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
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
Golden tips! Love content like that with different case scenarios and clear explanation! I have learnt so much! Thanks for sharing!
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 â€
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
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
It was worth to watch, I learned pretty valuable things especially the fetch abort, it's golden, thank you!
one of the best React tips I ever learn on CZcams. Thank you so much
amazing video for react beginners. :) Thank you. Looking forward for more react mistakes that beginners and more advanced devs make
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
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.
Hands down, what a perfect rhetoric - watched it with great pleasure - 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
This was really straight to the point and very helpful. Thank you Kyle! :)
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.
Really useful one. Please keep on making great informative videos like this. You're the best!
This worked incredibly well! I can finally play it thanks
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.
This is the single most useful video I've seen since I started React coding
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.
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.
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
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!!
Excellent explanation on state setter usage
Great video. I don't know what more can i say. Cheers!
It's very helpful for React beginner like me! Thank you for your videos :)
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!
You just prevented some lay offs, great job.
Thank you so much, as a beginner you helped me a lot
Excellent video, thank you very much.đ
Amazing! You make great content. I especially like your youtube shorts
Great video ! Well explained ! Thank you, I'm modifying my code right now...
best explanation of useMemo out heređđœ
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 :)
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.
Really good video, very informative and explaining in a clear way.
thank you for this great quality content
great tutorial, I learned something new today. Thanks :)
I really appreciate this video!! đ
It was amazing man. Thanks a lotđ„đ„
Well done sir, excellent video. Thank you for your hard work.
Nice tip last one.Thanks
I really appreciate your explanations. Top-notch!.
Amazing explanation! Many thanks
Many thanks! Good luck with your channel! Greetings from Kyiv!))
Thank you Kyle!
Thanks a lot. These are very important and useful knowledges.
that just makes so much sense!!!! thank you for bring the good code
Amazing video, thx a lot!
You really deserve thumbs up from me. Good Job. đ
last one just perfect! thanks!
Great video dude thanks :)
This is really helpful â€ïž
good explanation !!!, my problem can be solved, thank you very much..
This video rocked my world. Had quite a REACTion to it.
Thanks for video Kyle
Great video! useRef seems neat, but you do lose the ability to have real time validation, as that logic would be placed in the onSubmit function.
Good tips , thanks for sharing
00:45 tag stores fields value
Good video. One tip: if the arrow function will return an object, you can just put the object inside parentheses instead of using a full code block with a return keyword. Example: () => ({ age, name })
Also I believe you can simply return controller.abort instead of returning an anonymous function which calls controller.abort()
Would you be able to explain to me what is being passed to currentCount at around 6:00? Does calling setState automatically pass in the current state as an argument? Not sure how else it would be possible since the parameter name seems to be arbitrary, ie prevState. It sounds like you know your stuff, any help would be appreciated!
@@billynitrus setState accepts a function which its parameter (currentCount) is the value of âcountâ before being updated.
Ex. If count is 9 and you clicked on the â+â button ,if you try to log âcurrentCountâ you would get 9 ,thus âreturn currentCount (9) + amount(1)â will result in updating âcountâ to 10
Thanks. I didn't knew these.
i love react and i love this youtube channel, hi from indonesia
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.
Awesome explanation â€
excellent ! Big thanks
very simple and very useful!
super informative and helpful
I even express with words how much this video has helped me. I got answers to lot of my questions. Thanks Kyleđ„
Usefull for beginner like me, thanks đ
Great! Thanks from Brasil!!!
Very good, on point, thx
You are my hero.
Btw, I think that we all learned the hard way that adding the useState count twice in a row would still do it just once :P
that was helpful thank you
Soo good to see that there's finally more than just a guitar in your room :D just kidding, awesome video as always!
You are AMAZING ... Kyle đ
That last useFetch insight is very helpful! I think it could be even more so if combined with some king of debounce? So the fetch only runs after say 0.5s?
that useMemo trick... was lovely
Simple and brilliant
You would still control re-renders by using denounce on top of state. So, there won't be a need for ref in this case. As the react doc itself suggests us to go with controlled components over uncontrolled components
Useful video thank you
{} === {} false is the correct result for more than one reason but what I want to stress is that {} is NOT an object, it is the LITERAL CONSTRUCTOR hense don't tide the symbols to what they actually are, the constructors return objects.
Excellent video ty.
Thanks for all the react tips! Really helped me a lot :) will you ever put out a video of you playing guitar? haha
I'm pretty sure, that there is already a part in one of his videos, where he plays a solo... But I can't remember how it was called... đ
this is super helpful
best tips ever. i also was not using functional way of setting state
Thank youuuu very much
if its a simple form then you can just take the values from the form event when you submit and you dont really need to keep state provided you have a vary basic use case for the form, complex validations and connected models then you'll probably go back to using state
Thank you for share.
was great like always
Good work Kyle đ
thank you sir what was informative
Useful videoâ€ïž
Thank you for the great video! Regarding the choice between useRef and useState for form submission, I believe we should use useState instead of useRef. This is because we typically need to reset the input value to empty after submission. For input filtering, updating the state as the keystrokes change is necessary to display the latest value in the UI.
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
Great video! Iâm glad not making any of those mistakes đ
Thanks, A lotđ
Last tip was really important â€
Thanks Kyle. Funny how I'm an advanced react developer and I make a couple of mistakes you pointed out.
Learning so much đ
this video is all react people need, thanks a lot.