Full React Tutorial #27 - Controlled Inputs (forms) 

God*

thx

thanks king

Thank you good sir!

You dropped this 👑, king

thank you

That's fantastic to hear Susan, sometimes it takes a while to cement in, but once it does, hopefully it sticks :) I find that application and giving yourself little challenges help aid this even more so! (learn by doing).

I'm reading your recap in every video. That's really useful !!

@@yashrdoshi I still don't understand why exactly the value of the input needs to be set to the the dynamic value. And why it is letting him change the text in the input after he implements the onChange event. Would like to understand what happens in the background...

@@jackw.3978 Great question Jack! The onChange attribute fires everytime the value of the input is changed. And since the onChange event is grabbing a reference of the value attribute's value to set a state variable, we must set the value attribute to a 'dynamic value'. I hope this helps.

What I don't understand is why do we need to assign the value of an input since we don't use this in anything. When we need the value of that input, we use the state to process it(maybe pass it in the backend or something), not get the actual value reference from the actual element.

I have done the same, following courses from Udemy, but never fully grasping REACT as I also had issues with the tutors way of explaining too, until that is I found Net Ninja, he is a Legend!!!!

But where to go from here after finishing this series?

Good suggestion, personally I think it might be better to use the placeholder attribute, because if someone goes back to edit that field it will reset.

Thanks for watching Peter :)

Good luck

Got the job! Gonna sign up for the Udemy course.😎

@@TheRahulDBZ Thank you. Pretty stoked about it. 🚀

@@michaelandersen8570 any important tips you can give to someone like me who's looking to apply for jobs?

@@mistersir3185 I can only speak for myself, and to be honest a lot of it has to do with pure luck. Best tip I can give is to code as much as you can and put it on Github. Make your own stuff and take inspiration from tutorials in the beginning - but avoid pure copying. When you have built a few small projects you'll have confidence in yourself and it will reflect in the way you write about yourself in your resume. I think recruiters pick up on this. And it will also help tremendously at an interview.

That is awesome to hear Mels :) your support is much appreciated!

Thanks Wenlong!

That's brilliant to know :) glad it helped!

@@NetNinja do you have router v6 in this project?

Yes! Literally was just about to say this!!!

yaa me too...he is amazing at his work

Thanks!

Awesome! thanks for watching Rafael :)

Thank you! 😃 I made it myself

Thanks Jakub

Glad to hear it! Thanks for watching Adam :)

state is not variable, we are destructing an array when we say const [x, y] = useState(""). and this is the regular behavior of const. const is storing reference to the array which can not be changed/reassigned. but we are not changing/reassigning the array here. We are just changing one of the values/variables stored in the said array, in this case, the value of x. Hope this helps. also if you want to study further just search on youtube for something like "difference between const, var, and let in javascript"

If you look at this video (ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-dzEieWaOJE0.html) at about 4:14 it explains this fairly well. As Ali stated in his comment, this is an Array, and an Array (with Const) can be updated. The video doesn't talk about React, but about Const and when/if it can be updated.

No problem :) hope it was helpful

It is just laying around there but it is handy when you have images and other static stuff that will be okay to be open to see by the public. src and other folders are kinda private or you could say the stuff that only you could see means the source code and one more thing I want to tell you that you should learn next.js too as it would be more good and robust combination with react. And you can learn more about next.js in this video ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-Sklc_fQBmcs.html&t. I hope I helped you , have a nice day

Thanks for your support Jochen, it's much appreciated!

We create state using const but the state is not a data type so it doesn't act like a simple value. Process is done by state not const directly

Watch the useState video again, he already explained there

That is because when you make UseState(initialValue) in form you see initial Value in that field.

you sound like my project manager

@@TheRahulDBZ bruh😅

@@TheRahulDBZ lol😂

Actually yes. You need to define an object variable for the new BLOG content, something like: const [blog, setBlog] = setState({ title: '', body: '', author: 'mario' }) then your inputs + textarea something like (take care that every element has a NAME attribute because this is how you can identify them later): mario yoshi now, you can set all of your elements with just one function, handleInput: const handleInput = (e) => { setBlog({ ...blog, [e.target.name]: e.target.value }) } a) You need to be familiarized with the JS concept of destructuring, so "...blog" means we're getting all properties of "blog" (title, body, author) in a new element, not "blog" per se because it's immutable. b) [e.target.name] is basically: title or author or body. You need to understand that (e) is the event on the form elements. "e.target" is every element per se: the input, the select and the textarea. Then, "e.target.name" is the name of the element, so it's respectively: title, author and body. c) e.target.value: is the current value of the input, the select and the textarea. To finalize, when you need to post, you don't have to declare a new variable as in the video, you just post "blog": fetch(url, { method: 'POST', headers: 'Content-Type: application/json', body: JSON.stringify(blog) }) React needs you're familiar with some kind of JS concepts like deconstructuring; in the same way you will use .map() a lot to mapping arrays to construct DOM elements. At the end it's just practice, practice and more practice.

Hooks are another option that can be used to manage state as well as for other things. You can use the useState hook in a functional component for that component to have state, instead of relying on a class-based component for state. Props are not replaced at all by hooks, they are still very relevant and needed to pass data from one component into another. I covered props earlier in the course (lesson 11, 12, 13) :)

@@NetNinja it means, we don't need create state when using hook like create state in class component, right ? so anyway, thank you a lots for replying me

@@hoanglongpham5907 Hooks are used with functional components because functional components dont have state like class components do BUT by using hooks we can add state to our functional components.

We don't "track", we update it to the state variable