You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: curriculum/challenges/english/25-front-end-development/lecture-debugging-techniques/6733bee844600f35c05b8264.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,35 +14,35 @@ Watch the lecture video and answer the questions below.
14
14
15
15
## --text--
16
16
17
-
Which of the following is a common use case for `try…catch…finally` in JavaScript?
17
+
What best describes the `try` block?
18
18
19
19
## --answers--
20
20
21
-
Creating new HTML elements.
21
+
It’s for running code again automatically after an error occurs.
22
22
23
23
### --feedback--
24
24
25
-
Think about error handling when interacting with external data sources.
25
+
Think about the order of blocks in `try…catch…finally` statements, and the types of tasks each block handles.
26
26
27
27
---
28
28
29
-
Styling a webpage using CSS.
29
+
It’s for handling errors.
30
30
31
31
### --feedback--
32
32
33
-
Think about error handling when interacting with external data sources.
33
+
Think about the order of blocks in `try…catch…finally` statements, and the types of tasks each block handles.
34
34
35
35
---
36
36
37
-
Declaring variables.
37
+
It’s for setup before an error is thrown.
38
38
39
39
### --feedback--
40
40
41
-
Think about error handling when interacting with external data sources.
41
+
Think about the order of blocks in `try…catch…finally` statements, and the types of tasks each block handles.
42
42
43
43
---
44
44
45
-
Handling API requests.
45
+
It’s a safe wrapper for code that might throw an error.
0 commit comments