You are a genius

@@anknara1381 You are too kind. Thank you 🙏

Hi Dave, I have really appreciated your React tutorial and feel as though I have learned a lot from you. I am working on the context API video and it is 2022 post react router v6 release. I am having some trouble with understanding how to incorporate the context api correctly now that we have a different file setup when using Layout.js. Do you have any video/code that shows how you can use the context API with the newer version of react router while creating the blog app?

@@stevenbehm1 yes, search my channel for React Router and you will find the update for RRv6 which uses this same project 🚀

Thank you for the kind words! 🙏🙏

You're welcome! 💯

You're welcome! I'm glad it helped 💯

Thank you, Jimmy! 💯

Great helpful share - thanks! 💯

Thank you!

Absolutely! Prop drilling is a great way for beginners to start but we've discovered the context API is better 💯🚀

Spot on, my friend. If it works, they typically want you to move on. Best to refactor before telling anyone it works! 😂 Thanks for comment Ahmad. 🙏

​@@DaveGrayTeachesCode Looks good😁 , but now I need to find an excuse for the delay in delivery 🤔 Thanks for the great content Dave,

Glad it helped! 💯

You're welcome 🙏

You're welcome!

Glad to hear it helped!

You're welcome! Thank you for watching 💯🙏

I appreciate the kind words. Thank you! 🙏

Thanks for your feedback. I may eventually make short videos on hooks as you are suggesting. I'm nearing the end of this series now so I will complete it first. Thanks for watching! 🙂🚀

@@DaveGrayTeachesCode thanks sir you are doing a great job

You're welcome, Jeff! 🙏

@@DaveGrayTeachesCode do you have a video on how to create a way to call APIs?

@@thejeffkershner yes, I do. In this React series, I have lessons on using Fetch and later on in the series, Axios. I do recommend learning Fetch in Vanilla JS first with this tutorial: kzfaq.info/get/bejne/jNOBacd529SveYE.html

It sounds like you are understanding it. If you create state for just one component, it is ok to keep using useState in that component. If you need to share state between components, useContext helps.

Thanks!

You're welcome! 💯🙏

Each context we create has it's own provider property. We can have more than one context per app if we want. Likewise, we can use the provider to provide the context to all of the app (as you see in this example) or maybe just part of an app. For example, an account settings context may provide data that is only needed in a specific part of the app. {children} references all components inside the provider. We wrap the provider around the part of the app we want to provide the context to. You see this in the App.js for this example. I hope this helps. 💯

@@DaveGrayTeachesCode That makes sense David, thanks for the reply. But as confirmation, the function that returns the context is the function that will be the .Provider correct? Like in the code below, DataContext is returned inside of DataProvider, therefore DataContext knows that it's .Provider is the DataProvider function? const DataContext = createContext({}); export const DataProvider = ({children}) => { const [posts, setPosts] = useState([]); const [search, setSearch] = useState(''); const [searchResults, setSearchResults] = useState([]); const [postTitle, setPostTitle] = useState(''); const [editTitle, setEditTitle] = useState(''); const [postBody, setPostBody] = useState(''); const [editBody, setEditBody] = useState(''); const navigate = useNavigate(); const {width} = useWindowSize(); return ( {children} ) }

You're welcome!

Thank you, Sona! 🙏

Thank you!

React apps are SPAs = single page applications. When you reload / refresh, you are restarting the application. A reload / refresh erases the current state of your application. We use React Router to simulate navigating to different pages on the web while maintaining the app state.

@@DaveGrayTeachesCode thank you for help, for solving this should we send some of data through props? i just need a tip to go and study about it

I do plan to cover Typescript in the near future 💯🚀

It helps you avoid drilling props through multiple components. This can become cumbersome especially when the intermediate components do not need the props that are being drilled.

@@DaveGrayTeachesCode Thank you for the clear explanation as always Dave 😀

I do not, but testing is one topic I want to cover yet this year.

@@DaveGrayTeachesCode :( Would love to see those when you do them, You have a great way of teaching and easy to follow. Thanks for all so far.

Thank you! 🙏😀

Hmm, I haven't seen that and don't think I was using RevealBase in this tutorial - but a dependency may be. Sounds like you could either not use strict-mode or update the component they suggest you update.