1
00:00:00,360 --> 00:00:06,960
All right, so now we are here in our app once again, and if you remember, within our year after year

2
00:00:06,960 --> 00:00:11,730
scored, we already have not used any rating so far.

3
00:00:11,730 --> 00:00:16,080
And the score is actually working fine for any problem because the players action number is already

4
00:00:16,080 --> 00:00:18,180
going to take care of most of the hard work for us.

5
00:00:18,390 --> 00:00:24,450
But we can try to make things even more problematic over here in the car so that we can actually see

6
00:00:24,450 --> 00:00:25,530
if that works or not.

7
00:00:25,830 --> 00:00:27,750
But we are actually going to do that in this video.

8
00:00:27,750 --> 00:00:33,570
We're actually going to see how we can perform a debug operation so that that particular trick can actually

9
00:00:33,570 --> 00:00:38,620
help us to perform some more way to perform the Veidt operations and stuff.

10
00:00:38,940 --> 00:00:44,910
So what I want to do is in order to debug this code execution in the to record it is much, much simpler,

11
00:00:45,090 --> 00:00:46,220
pretty much like C sharp.

12
00:00:46,230 --> 00:00:50,010
Our Java or any of the language bindings are only going to do this.

13
00:00:50,160 --> 00:00:55,830
You can just put a breakpoint on the place that you want to perform or debug operation like this red

14
00:00:55,830 --> 00:00:57,570
color over here.

15
00:00:57,570 --> 00:00:58,920
And they call this breakpoint.

16
00:00:58,920 --> 00:01:03,720
And once you put the breakpoint, we now need to run the code there debug mode.

17
00:01:03,990 --> 00:01:08,850
I mean, in the department, if you just run the node controller, just this is not going to hit that

18
00:01:08,850 --> 00:01:10,950
particular breakpoint because this is not the debug.

19
00:01:11,730 --> 00:01:15,900
Rather, if you go over here, there is something called as a run option.

20
00:01:16,020 --> 00:01:19,760
If you just like that, you can see that there is something called a run and debug.

21
00:01:20,070 --> 00:01:26,160
So this run and debug will actually help us to run the particular code and also help us to debug the

22
00:01:26,160 --> 00:01:26,540
cord.

23
00:01:26,550 --> 00:01:31,770
So if I hit this run and debug, you can see that it tells me or brings me up different options like

24
00:01:31,770 --> 00:01:36,870
Chrome Preview, Edge Launch, Norges Legacy, Norges Prevue.

25
00:01:37,230 --> 00:01:41,880
So I'm just going to take the Norges Prevue option because this is even though it's a preview, does

26
00:01:41,880 --> 00:01:42,720
the job pretty well.

27
00:01:42,990 --> 00:01:45,090
And I'm just going to choose this option for us.

28
00:01:45,480 --> 00:01:51,050
And once I do that, you can see that it is going to start performing the action for us over here.

29
00:01:51,510 --> 00:01:57,090
So just ignore about these issues because they're going to be looking at the terminal stuff and you

30
00:01:57,090 --> 00:02:00,690
can see that it is just going to run on the debug mode.

31
00:02:00,960 --> 00:02:07,470
And once that particular line comes in, just wait for the debug operation to complete, which is pretty

32
00:02:07,470 --> 00:02:07,850
cool.

33
00:02:08,100 --> 00:02:13,860
I mean, this trick is something we'll be using for the rating mechanism to see if that rate mechanism

34
00:02:13,860 --> 00:02:15,900
actually works or not in our next video.