I hope you enjoy watching it as much as I enjoyed making it. If you have any questions or comments, feel free to leave them below and I'll do my best to respond. And don't forget to like and subscribe to my channel for more great content!
I've same use case but in my case I need to pass only 2 props value (username and password) out of bunch of state values from my one sibling to another.
Yes, when state is lifted up to a parent component in React, changes to that state can trigger a re-render of the parent component. This is because when the state is updated, React will re-render the component and its children to reflect the new state.
@@exacode So... is it possible to prevent this full rerender without advanced state management? I've been banging my head against this wall for a while. Thank you!
@alanhf I think you can make the child components pure component using React.memo() that will stop the pure component being re-render if the props for that component are not changed. However the parent component will still re-render ( since state is changed in parent) and its all the non pure child components will also rerender.
@@exacode I was saying about page refresh that happens when u up state with that function. This was my mistake that it didn't work. Ur video was rly helpful ,tnx
@@freeversion825 When we are updating state, then React automatically re-renders the component and shows the latest state in the screen. This "re-rendering" is similar to page refresh but not exactly. Because here in re-render it does not refresh the entire page instead the specific component where the state got updated, it just re-renders that specific component. In this example we are updating the state in parent component. And in React when we update the state in parent component then it re-renders all of its child components. This is the default behaviour of React. Hope that helps! Let me know if you have any further questions or doubts.
This doesn't seem practical. Not every component is rendered in App.js. Unless one has to create a non-rendering parent component. I will recommend avoiding this method and using Redux instead.
@iprocoder It doesnt have to be app.js though. You can lift a state to any parent component and sibling components in that component can both have access to it.
I hope you enjoy watching it as much as I enjoyed making it. If you have any questions or comments, feel free to leave them below and I'll do my best to respond. And don't forget to like and subscribe to my channel for more great content!
As a beginner in react this method is really useful to me , thanks brother!
Glad it was helpful!
Bro it feels so freaking easy after your explaination... Thank U... I had a huge confusion here.. And U just cleared it... Thank U again❤
Thank you. I am new to Rect.js and this video helped me solve my assignment
Thank you for the lesson!!!!
Glad it was helpful!
I've same use case but in my case I need to pass only 2 props value (username and password) out of bunch of state values from my one sibling to another.
Code for Expo = React native ?
Are both same ?
very good explaination
Amazing video 🤝🤝🤝🤝
Glad it was useful!
nice video...❤❤
Osm video sir nice explain
Glad it was helpful!
Very Helpful Thanks Sir🔥❤
Glad it was helpful!
Thank you
nice explanation
👍👍
Glad it was helpful!
But lifting state won't cause a rerender of the parent component?
Yes, when state is lifted up to a parent component in React, changes to that state can trigger a re-render of the parent component. This is because when the state is updated, React will re-render the component and its children to reflect the new state.
@@exacode So... is it possible to prevent this full rerender without advanced state management? I've been banging my head against this wall for a while. Thank you!
@alanhf I think you can make the child components pure component using React.memo() that will stop the pure component being re-render if the props for that component are not changed.
However the parent component will still re-render ( since state is changed in parent) and its all the non pure child components will also rerender.
How i prevent refresh?
I didn't understand your question, could you please elaborate which refresh you are referring to?
@@exacode I was saying about page refresh that happens when u up state with that function. This was my mistake that it didn't work. Ur video was rly helpful ,tnx
@@freeversion825 When we are updating state, then React automatically re-renders the component and shows the latest state in the screen. This "re-rendering" is similar to page refresh but not exactly. Because here in re-render it does not refresh the entire page instead the specific component where the state got updated, it just re-renders that specific component.
In this example we are updating the state in parent component. And in React when we update the state in parent component then it re-renders all of its child components. This is the default behaviour of React.
Hope that helps! Let me know if you have any further questions or doubts.
This doesn't seem practical. Not every component is rendered in App.js. Unless one has to create a non-rendering parent component. I will recommend avoiding this method and using Redux instead.
Thank you, I'll read about Redux. But this method is pretty useful for beginners...
@iprocoder It doesnt have to be app.js though. You can lift a state to any parent component and sibling components in that component can both have access to it.
Yes correct