1
00:00:00,530 --> 00:00:03,430
We found the problem by
jumping inside a function and

2
00:00:03,430 --> 00:00:07,700
experimented by changing
the options in the debug console.

3
00:00:07,700 --> 00:00:11,200
But there's another way you can
experiment while debugging and

4
00:00:11,200 --> 00:00:13,630
that's by editing the code life.

5
00:00:13,630 --> 00:00:17,070
If we trigger the break-point
again by refreshing the page,

6
00:00:17,070 --> 00:00:20,730
on line 42 we can see that
the reversed variable

7
00:00:20,730 --> 00:00:26,030
is being passed into the local variables
that are accessed by the template.

8
00:00:26,030 --> 00:00:29,551
This is where we should be passing
in the original variable too.

9
00:00:31,720 --> 00:00:35,660
I can directly edit the line
on 42 to test it out.

10
00:00:38,491 --> 00:00:40,652
This doesn't save the file to disk,

11
00:00:40,652 --> 00:00:44,150
it's editing the code running
in the computer's memory.

12
00:00:45,450 --> 00:00:50,270
When we hit Resume, it works.

13
00:00:50,270 --> 00:00:55,343
We can temporarily disable the breakpoints
with the Deactivate Breakpoints button.

14
00:00:57,387 --> 00:00:59,708
And we can test out some other routes.

15
00:01:04,227 --> 00:01:05,460
And it works, great.

16
00:01:07,100 --> 00:01:11,710
You still have to use your code editor
to include your fix there too, and save.

17
00:01:13,140 --> 00:01:17,330
I hope you enjoyed seeing some of
the debugging tools available to you, and

18
00:01:17,330 --> 00:01:19,560
how they can improve
your development cycle.