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: README.md
+12-1
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,7 @@ your IDE should open up. You'll see a sidebar like this:
49
49
50
50

51
51
52
-
If you open up that "javascript-logging-lab..." folder, you'll see a list of files (along with a test/ directory). Click `index.js`, and it will open in the editor.
52
+
If you open up that "javascript-logging-lab..." folder, you'll see a list of files (along with a test/ directory). Click `index.js`, and it will open in the editor.
53
53
54
54
In `index.js`, you should see, well, nothing. We'll fix that soon.
55
55
@@ -140,6 +140,17 @@ We'll try to rewrite these error messages when possible to be more descriptive a
140
140
141
141
Now it's your turn — can you follow a flow similar to the one we followed together above to get the remaining to tests to pass?
142
142
143
+
Imagine that you're building the user interface for a fancy ATM machine.
144
+
Because the developers are hip with the latest trends, they're using
145
+
JavaScript for the user-facing parts.
146
+
147
+
We need a way to send messages to the user: some messages are just updates,
148
+
some are warnings (the user should not continue doing what they just did),
149
+
and some are errors (something broke, and we need to recover).
150
+
151
+
Your job is to identify a way of sending each kind of message. Hint: in
152
+
JavaScript, you'll probably find ways of telling users things with `console`.
153
+
143
154
When all of your tests pass, be sure to run `learn submit` to move on to the next lesson.
0 commit comments