7 ms·
Your first example is pretty malformed. If you're promise-chaining why would you be trying to assign to variables in the outer scope? Why are you assigning to c
by likeclockwork 8y ago
Your first example is pretty malformed. If you're promise-chaining why would you be trying to assign to variables in the outer scope? Why are you assigning to constants? Why are you calling somePromise a second time in the first then?
It's almost a strawman. Anyone would have written:
somePromise()
.then(anotherPromiseFuncThatNeedsP1)
.catch(e => whatever);
- olingern 8y ago- re: const assignments: you're correct. I did not compile this and the assignments should use let. - Show me where you have access to p1 outside of your closure. The idea is / was -- you need access to both p1 and p2 for some comparison. The first `somePromise` would have been more accurately written `someInitalPromise` The point is that try/catch + async & await removes a lot of cognitive overhead. Before async/await I rarely used try/catch -- so it's easy to get things done without it, but the combination of the two aforementioned has made codebases I work on much easier to maintain.