Hot take: Promise.prototype.finally should never be used. Use async/await + try/finally instead.pic.twitter.com/O4TDmwQhIe
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Hot take: Promise.prototype.finally should never be used. Use async/await + try/finally instead.pic.twitter.com/O4TDmwQhIe
Hmm.. simply because you think async await is better is not an argument... can you be more explicit ?
The link in the article explains it.https://twitter.com/mathias/status/922462717109092352 …
Not so exciting, this feature is completely replaceable by adding another `.then` at the end.
That’s not entirely accurate. In the code example, consider what happens if `elements` is `undefined`.
finally!
This example might be not very representative since `finally` in this context is equal by functionality to `then`.
Even when element would be undefined?
finally!
If you place a .then() after the final .catch() it's effectively the same as .finally() and works in all major browsers.
then() and finally() are difference. The function you pass to catch() could also throw, so the following then() would not be called.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.