1
00:00:00,210 --> 00:00:06,420
All right, and welcome to our next project, the Jobs API, where we'll finally combine our knowledge

2
00:00:06,600 --> 00:00:14,190
with crowd functionality and as a result will have an API where users can log in and manage their job

3
00:00:14,190 --> 00:00:18,360
search during the project will also learn how to deploy our app to Hiroku.

4
00:00:18,630 --> 00:00:24,600
So our apps on the cloud and set up nice documentation with Swagga.

5
00:00:24,600 --> 00:00:31,150
UI for this project are still managed to build a matching front end up but moving forward.

6
00:00:31,440 --> 00:00:37,680
So in our future apps, I'll exclusively use documentation to showcase the end result, since building

7
00:00:37,680 --> 00:00:41,780
a front end project for every API is just too time consuming.

8
00:00:42,270 --> 00:00:45,630
And before we take a look at the features, let me stress one more time.

9
00:00:46,110 --> 00:00:48,360
Our job will be setting up the API.

10
00:00:48,570 --> 00:00:49,590
So the back end.

11
00:00:49,920 --> 00:00:51,210
The front end is there.

12
00:00:51,210 --> 00:00:57,960
Just to give you a better overall perspective on how the API is going to be consumed in real life.

13
00:00:58,320 --> 00:01:04,410
And basically the idea is following where we have some kind of front line application and we can log

14
00:01:04,410 --> 00:01:05,730
in or register.

15
00:01:05,970 --> 00:01:10,860
So of course, if I haven't created my account, then first I would need to register.

16
00:01:11,160 --> 00:01:16,040
So I go over here and then I'll type some kind of gibberish on so that I'm Peter.

17
00:01:16,440 --> 00:01:21,680
The email will be Peter at Gmail, not come, and then we go in secret.

18
00:01:22,020 --> 00:01:29,670
Now, regardless whether you're logging in or registering, we'll be sending the token legist and web

19
00:01:29,670 --> 00:01:36,180
token and not on the front end will right away be able to showcase the user account.

20
00:01:36,450 --> 00:01:43,020
So if I go here and if I say that I want to register and if I submit, if I provide the correct values

21
00:01:43,260 --> 00:01:44,670
now I can see my dashboard.

22
00:01:44,670 --> 00:01:47,250
Since I just created my account, I have no jobs.

23
00:01:47,370 --> 00:01:51,210
So of course in here I just need to provide the values to go with Apple again.

24
00:01:51,210 --> 00:01:54,660
And I'm going to be looking for front and position.

25
00:01:55,050 --> 00:01:56,880
I submit now I have my job.

26
00:01:56,970 --> 00:02:02,840
I can delete the job, I can edit the job, and I can also take a look at this single job.

27
00:02:03,360 --> 00:02:11,520
So in this page, I'm actually fetching data about that one single job and I have functionality to edit

28
00:02:11,670 --> 00:02:13,320
once I change some values.

29
00:02:13,740 --> 00:02:22,050
Now, when I'm sending this HTP request, this is going to be a patch request edit and if I provided

30
00:02:22,050 --> 00:02:25,590
the correct values, then I successfully modified the job.

31
00:02:26,010 --> 00:02:30,750
So now I can go back to the dashboard and I see that I have my job.

32
00:02:30,960 --> 00:02:36,050
But in this case, instead of spending, which is going to be the default because we have the interview

33
00:02:36,300 --> 00:02:43,350
and if I'm no longer interested or maybe they send me a rejection, I can also remove the job.

34
00:02:43,770 --> 00:02:47,070
And once I do that, I have no jobs to display.

35
00:02:47,610 --> 00:02:54,140
And as a quick side note, if you're just interested in the front end project, navigate your Johnson

36
00:02:54,150 --> 00:02:54,830
on dotcom.

37
00:02:55,200 --> 00:02:58,080
And at this point, it is still on our homepage.

38
00:02:58,380 --> 00:03:05,100
But if you don't see it there, it's always going to be available in the projects page and you can quickly

39
00:03:05,100 --> 00:03:05,530
find it.

40
00:03:05,550 --> 00:03:10,080
If you look for YouTube now, YouTube doesn't mean that the project is going to be on YouTube.

41
00:03:10,500 --> 00:03:13,460
I'm just grouping my projects that way online.

42
00:03:13,470 --> 00:03:19,140
And here you can take a look at the application if you click on this massive, massive button.

43
00:03:19,500 --> 00:03:24,480
And if you want to take a look at the source code, just look for star files or complete.

44
00:03:24,480 --> 00:03:29,700
Both of them actually go to the same repo and learn in the source.

45
00:03:30,030 --> 00:03:36,360
You'll be able to find everything and a few things to know about the project when it comes to the URL.

46
00:03:36,640 --> 00:03:44,520
Of course I'm using my API, so if you want to clone the project and test it out on your back and you

47
00:03:44,520 --> 00:03:48,940
just need to change the URL and that is in the Axios address.

48
00:03:48,990 --> 00:03:55,140
So in the source, I have access to jobs and as you can see, the URL is pointing to my back end.

49
00:03:55,140 --> 00:03:59,460
But if you want to test that out on yours, you just need to change the arrow.

50
00:03:59,820 --> 00:04:03,540
And lastly, keep in mind that I recorded this in July of twenty twenty one.

51
00:04:03,990 --> 00:04:10,890
So eventually, once the React 113 is stable, I might refactor the code to take advantage of the new

52
00:04:10,890 --> 00:04:11,400
features.

