All right.
And once we have the structure for both, for us as well as jobs, now what we can do the market.
I'm going to close all the tabs just so it's less busy here and I'm going to navigate to a postman and
test that out, whether we're getting back all those dummy strings.
Because if everything's in place, if everything works fine, like I said, start setting up the model
and one by one, we'll start working in the controllers.
So I'm going to navigate back to the as you can see, I have a clear workspace.
I have no collections.
And in this case, I don't think I'm going to use the environment.
I'm just going to set up everything globally again, if you know how to set up an environment.
You can definitely do so.
But that's not going to be my case.
Just keep in mind that eventually, once we save the token here in the postman, I'm going to use the
global approach.
So I'm going to save it as a global variable.
So if you are going with environment, your code is going to be a little bit different.
But of course, I'm going to cover once we get there.
And for starters, I want to create a collection.
I'm going to give it some kind of name.
My gosh, I'm going to go with geography and let me go with all uppercase.
Just because one, we want to set up two more folders here, so we want to go with our folder and in
this case, I'm going to go with jobs.
And then the second one will be the fourth one.
So one more folder.
And a folder, and let's go with us.
So I'm going to go with rename and then off and let's actually start working in the office because I
think it's going to be a little bit faster.
I'm here.
Let's add a request.
So it's not going to be a good request right from the get go.
We want to give a different name, so say register.
User, and it's not going to be a greater focus, like I said, it's going to be a post request and
since we're pretty much going to be repeating the localhost 5000 and the API version one and all that.
Why don't we set it up as a global variable right from the get go?
And you can do that by clicking on the sign and where we have the globals when just go with add and
I'm going to go with your URL and the initial value you're going to be following where I'm going to
navigate to my local host 5000, I should see the welcome I do.
So that's an awesome start.
And then let's copy and paste in.
Like I said, we're going to go with API and then a version one and then we'll go forward slash off
for its nice jobs and hopefully you get the gist.
I'll save this one.
Back in the register user, I have the post request, which is awesome.
And then if I want to access the URL, I'm going to go with double curlies and then I'm going to close
this one and then I'll go with forward slash and burn off.
And then more specifically, looking for the register one now, and surely I'll pass in some values,
but not for now.
So I'm just going to send it.
And if I can see right through user, we are already on the right path.
That means that you are always working well.
That means that the register function is going to work eventually.
And if I'm not going to make some egregious errors, that also means that pretty much the rest of the
rules are going to be good to go as well.
So now in this case, I just want to copy this one and then I'll rename this one.
And by the way, instead of renaming actually went with copy one more time here.
Let's go with your name, and then let's call this log in.
Still going to be a post request, so that stays the same.
Me.
Read more These types there so.
Well, memorial state and log in post request.
Start off the register or welcome for login again or send.
Yep, we have logging in user.
That's awesome.
And then let's copy this one more time.
Let's rename it right away and say Update Update user.
Now this one will be patch.
So let me make sure that I show and navigate to this one.
And then I'll close the log in one patch right here, and then let's go and update the user update.
Here's there, and then I'll mess up some things on a purpose just so we can see whether our error handling,
meaning the URL does not exist, works.
And as you can see right away, even without doing anything, actually have a rule does not exist.
So this is the case where I need to go back and check it out.
What was my actual root?
So back in the Arthur outs, I have update user or it's lush and this should be update user.
And for some reason and off and an update user, I have doesn't exist.
And the reason for that is following where I didn't set up a patch.
My apologies.
You see how easy it is to make a mistake.
So I was going to mess with this one.
The ITBP were in here in the post, man, but I didn't have to do that since I have a bug here in the
arthropods.
So that's how we can know that everything works as far as our error handling as well.
So now I can clearly see I'm that user, which is what I was expecting.
So that should do it for us.
Now we want to do the same thing for two jobs.
So let's go with our request.
The first one will be create job.
Great job.
And this one will be a post request and we use the same URL here.
So you are all online forwards and then jobs, because remember, that was our route throughout.
So let's say this one, Senate and yep, we have great job.
So now let's keep on moving.
And basically, I'll just to placate them.
I believe I had five.
Correct?
So what was it for?
And then one more.
So let's do that or not.
Some reason I decided to delete.
That's not what I wanted.
So now I have five of them, one by one.
I just need to change them around where, first of all, this is not going to be create jobs and get
all jobs.
One, we will set up a get request.
So this is going to be for all the jobs that send up that we have got all jobs.
That's awesome.
Then we want to go with, let's go with stats here.
We're going to go with stats.
I'm going to call this show stats.
And this is going to be a get request and let's send it to show stats.
And then we have one for update and one for delete.
So we're going to go here with jobs.
And then I'll just pass in some dummy value, I'll say one, two, three.
So that's going to be my idea.
Now this will be a patch one and the name here is going to be update job the job.
But Senate, yep.
And then lastly, we have one for the as well, so delete job, and now let's do the same thing one,
two three.
And instead of post, we're going to be looking for delete.
Let's save all of them before I forget.
And then go back to delete.
Send that and I can clearly see delete job.
And once we test everything, once we can clearly see that we're getting the correct values now, I
can start setting up our first model.