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
Missing newline or incomplete reason why a multi-string isn't created correctly.
Steps to reproduce
Open the lesson: Learn > Simple Types > Multi-line strings
Tap the top right button: Next
Tap the OK button on the Multi-line strings popup
Answer the first two questions correctly
The third question Review (3/8) shows:
var henley = """I am the master
of my fate
I am the captain of my soul"""
(Note: That's what it looks like on the iPhone X screen. But from the definition below, the first line, from var to fate, is a single line that's line wrapped after master to fit on screen. The issue below is unrelated to how it appears on the iPhone screen.)
"answer": "var coleridge = \"\"\"\nWater, water, everywhere\nand not a drop to drink\"\"\"",
"reason": "The final three quotes must be on a line by themselves."
And here the reason matches the question.
The intention might have been for the henley variable assignment question,
to also have newline \n after the first three quotes.
Because then there would be two questions with the reason:
The final three quotes must be on a line by themselves.
And three questions with the reason:
Multi-line strings must start and end with three double quotes on lines by themselves.
Actual behavior
The reason that appears when the question has been answered:
The final three quotes must be on a line by themselves.
Only mentions the second problem with the multi-line string variable assignment.
It doesn't mention that the first line with the three quotes also needs to be on its own line.
Or if, as suspected above, the reason is correct, then the question just needs a newline \n between: """ and I am
Before
"answer": "var henley = \"\"\"I am the master of my fate\nI am the captain of my soul\"\"\"",
After
"answer": "var henley = \"\"\"\nI am the master of my fate\nI am the captain of my soul\"\"\"",
Environment
Unwrap app version: 1.5
iOS version: 14.7.1 (18G82)
Device: iPhone X
The text was updated successfully, but these errors were encountered:
Missing newline or incomplete reason why a multi-string isn't created correctly.
Steps to reproduce
Learn > Simple Types > Multi-line strings
Next
OK
button on the Multi-line strings popupThe third question
Review (3/8)
shows:(Note: That's what it looks like on the iPhone X screen. But from the definition below, the first line, from
var
tofate
, is a single line that's line wrapped aftermaster
to fit on screen. The issue below is unrelated to how it appears on the iPhone screen.)This question seems to be defined here:
Unwrap/Unwrap/Content/SixtySeconds/multi-line-strings.json
Lines 48 to 49 in 3a5ee7f
The text, with the reason it was false, appears below the question.
Expected behavior
The reason should indicate both problems. The first and last three quotes should be on their own lines.
Possibly like the other questions:
Unwrap/Unwrap/Content/SixtySeconds/multi-line-strings.json
Line 41 in 3a5ee7f
Or if the intention was to have a newline after the first three double quotes.
Then a
\n
newline should be added.Another question with the same reason has a newline after the first three quotes:
Unwrap/Unwrap/Content/SixtySeconds/multi-line-strings.json
Lines 36 to 37 in 3a5ee7f
And here the reason matches the question.
The intention might have been for the
henley
variable assignment question,to also have newline
\n
after the first three quotes.Because then there would be two questions with the reason:
And three questions with the reason:
Actual behavior
The reason that appears when the question has been answered:
Only mentions the second problem with the multi-line string variable assignment.
It doesn't mention that the first line with the three quotes also needs to be on its own line.
Or if, as suspected above, the reason is correct, then the question just needs a newline
\n
between:"""
andI am
Before
After
Environment
The text was updated successfully, but these errors were encountered: