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
Your submission results compared to the expected:
ACTUAL EXPECTED
────────────────────────────────────────────────────────────────────────────────
"DR. MANHATTAN" == "DR. MANHATTAN"
"" == ""
────────────────────────────────────────────────────────────────────────────────
✓ Submission results match expected
✗ You didn’t create or didn’t use attachTitle method
# FAIL
Your solution to Values and promises didn't pass. Try again!
This IS returning a value at the end of the day, which is the point of the lesson?
The text was updated successfully, but these errors were encountered:
awitherow
changed the title
Exercise 8: failing with use of Promise.resolve?
Exercise 8: failing due to resolution with function call?
Apr 5, 2017
awitherow
changed the title
Exercise 8: failing due to resolution with function call?
Exercise 8: failing due to fulfillment with function call?
Apr 5, 2017
The point is here I think, workshop wants to show us although our function does not return a promise, onFulfill handler wraps it in a promise. So, this is why workshop expects us to use a function which does not return a promise and chain it with .then like it turns one! You are using your function (even invoke it) in resolve, so this is very usual. You are resolving a value there (from your function). Thus, you only chain two pieces: A promise and another function.
To sum up, workshop wants to emphasize if I don't understand wrong is that:
Promise -> .then -> function not returning promise -> but again .then -> another function
I have seen that the correct solution is returning a value, then passing that value to the attachTitle function, then console logging.
I did this approach and am failing for the reason shown also below.
This IS returning a value at the end of the day, which is the point of the lesson?
The text was updated successfully, but these errors were encountered: