Nice job.
And we're finally ready to kick things in full blown gear by getting the followers as well as the report.
And in order to make things even more interesting, I search for some awesome developers so I can look
for different reports as well instead of just repeating the same old, same old.
And we're going to start by looking at our response.
So if we head back to our project and then in the context.
We noticed that, of course.
Yeah, we have the response.
We set up get Abuzer and all that is fine.
So what I would want to do right now, though, well, in the read me, I can see that I have to you
URL's.
I have the one Forder repos as well as I have one for followers.
Correct.
So why don't we just take this particular one and I'm not gonna paste them in a tab.
Think we can just do it directly in a context because well we already have spent enough time with the
get up API and all that.
I'm just gonna place a comment and we're gonna copy and paste.
So that's the first one that is gonna be for my repose.
And then the second one will be my followers.
So again.
And let me navigate back to my read me online.
We're looking for this bad boy.
Let's get that sucker in there.
And we're gonna have another set of comments.
Copy and paste.
And we're just gonna say fall Lorsch.
All right.
So those are two.
You are odds that we would want to hit.
Let's take a look where we have the data.
So we have our sponsored data.
Correct.
So in that data object, we should see our user like.
So remember, when we're checking for the user if the response is successful.
This was our user object.
And of course, you can find that data in the mock user as well.
And what we're looking for here are two properties.
We're looking for the Log-in.
And then we're looking 40 followers.
You are all sorry, not following.
We have followers, Yoro, where again we have the ruled.
You are all users.
And then the user name.
And then the followers.
So those are two things we're looking for.
All right.
So let's set this up.
We have response.
We have response data.
So first, I would want to set up my user.
That's number one online concert.
And then we're going to the structure out the log in, man, follow worse.
So and then underscore you are all let's look for a response.
Online data.
So once I have these two properties, then, of course, I could set up two more quests.
Correct.
I have my axios and everything so I could simply say axios.
And now, of course, we just need to structure our request.
So again, I'm gonna go with template string.
I'm going to go with Roll TRL here.
So we're going to say roll to your URL.
So this is just for your reference, just in case you get confused of what I'm typing out here.
So essentially now I'm constructing this one that matches the user that we just searched.
So I'm going to go with route.
You are real.
Then I'm looking for the users and then the logging property because that's where I can find my user.
The logging property is the one that tells me, yeah, that's the user that you are searching for.
So logging that I'm looking for the repos.
And then I'm going to add that query parameter where I'm going to say, yeah, get me hundred dollars
per on line.
We go with on the score page, not as equal to a hundred.
So that should get me my reports.
And right away I could add a dot of van online.
I'm gonna get response.
And of course what I want is to grab that data and then place it where I have the repos.
Correct.
And I'm going to do the same thing for followers.
So I guess let's start simply by looking at our response response.
So that's my callback function and yes.
Will console log it just so we are on the same page.
No worry.
I don't think we'll use up all our requests while we're setting this up, because essentially this is
gonna be one of the last things that we're doing as far as the GitHub API.
So let's just look at the response more here and now.
I'd want to copy and paste and set up the same thing for my followers.
So we're going to copy paste.
And then the setup is going to be almost the same.
But, of course, the your health changes.
So let me add here a comment where I'm going to say repose online.
We're going to go with followers.
While the word selection and what is the you are out?
Well, we have followers.
You are all correct.
Want to double check?
We are followers, Yoro.
And then we just want to add that flag.
I would want to add per hundred.
Correct.
So let's do it.
We're going to remove everything now.
We don't need to reroute.
You are all anymore because I can directly get my repose and all that.
I'm going to simply say, all right, get me the followers here.
Followers, you are all online.
Forward slash or I'm sorry, not forward slash.
We're going to go with a question mark and we're going to say Per.
On this score, page.
Page.
And that is going to be equal to a hundred.
Let's save it and then let's use one of those other awesome developers.
Otherwise, I'm just showing you was Mascotte, Scott Dolinski and Brad Thavasi.
And we're gonna go with Sara Dresner, which is just an awesome, awesome developer.
And she has a lot of autonomy.
I would even say a free source help material all over the Internet.
So we're gonna go back to our starter.
We're going to copy and paste or get up user.
You are on there it is.
Now we're getting information about Sara.
If I'm going to inspect, I should have two objects.
Correct, because I'm console logging.
My response, I'm not as far as the data notice.
So this is for repos.
That's why I have eighty six.
And then this is gonna be forty followers.
And I'm here, of course I'm going to get at least a hundred because there's tons of people who follow
her.
All right.
Now what's left to do is to, of course, set up some kind of functionality where what I would want
is to use the set and line.
We're looking for repos and then we pass in the response and line.
Where was the repos while it was still on a dare?
Correct.
So I have response and then data.
We pass that one in.
And we're doing the same thing here where instead of followers, we're armed.
Sorry, instead of repos, we're going with set and line followers.
So said followers.
And we're passing a response.
And then again, data.
So set this up.
Now we're gonna go with Cassidy Williams, which probably has the most funniest Twitter videos you ever
seen.
I mean, she's just hilarious.
So we're gonna go with Cassidy, though.
I believe I'm pronouncing this correct.
Yeah.
Casado and man, we're looking for get Abuzer copy and paste and line here.
We should see the information about her.
Correct.
So as we're looking at it.
Notice we have languages were we have the most popular repos.
We have most for as well as the languages.
And my probably personal favorite is Jason, because of all the awesome work has done for the Gadsby.
I mean, he has been tremendous influence on the way he presents himself, the way he approaches people
and all that.
So I would definitely put him as one of the top people who spreads the word of Decode.
So let me just get him.
We're gonna go with Jason here.
And yes, my apologies.
I'm really bad on remembering the user names, so that's why I implemented some help over here.
So we're gonna go back in the starter.
We're going to copy and paste.
And once we search, of course, now we display everything that we need.
So now we're displaying the information about Jason as far as the GitHub and then the followers as well
as the reports.
So that's how we can set up our initial functionality where not only we get the user info, but also
we're getting three repos as well as the followers.
So now if I go back to my one, I'm going to go back to John hyphen Smellier.
Then, of course, there it is.
Now I'm displaying the repos for me as well as the followers.