jazad136 / react-udemy-github-finder2 Goto Github PK

I don't know how far this class is going to take me, but I want to stay focused on a main goal of mine, which is to go beyond a search bar and request things from some backend that I wrote. Even if it's creating a JavaScript backend (not ideal).

Replace old GitHub Finder code with Hooks. Hooks are weird. They encapsulate functionality however, that can help reduce variable length. Such a change at this point is welcome.

Starting Jan 25, document examples where notable examples of updating this project to use hooks and reduced functions and variables appear.

Stylize this project. Use my info rather than course provided info.

The concept of assigning values from my Github Finder's original App to my GitHub Finder's state object is really hard to grasp.

The problems:
I'm finding it hard to pass values from the returned search results to my User.js file.
Originally, App.js was passing down a "users" array to the Users object which would then loop through and map each users entity to a "user" object without much code. And each user would be passed as a prop to a UserItem. This part makes sense.

However, there's another route called "User.js" headed by url "/user/:login". Supposedly it took in all the props passed down to it.

However, it's not the job of "search" to get that "user" property, it's the job of the getUser function of App.js.
I think I know what I need to do. I'm hoping that just calling githubContext.user in User.js will do the trick, since we have already moved the "current user object" with name "user" to GithubState.js.

Destructuring is hard. Capture all examples in this issue where I'm de-structuring JSON Examples in my code, so I can learn how this can be done in many scenarios and follow along easier when this gets demonstrated again.

Transitionary comments that show how different states of the application progressed between completion of tasks are very helpful. Catalog these by tagging specific commits with this issue.