@jaffathecake I believe substack had a good rant on the matter. I'm mostly confused by the whole API, feel it does too much.
-
-
Replying to @yoshuawuyts
@yoshuawuyts I cleared up the confusion around that https://jakearchibald.com/2015/thats-so-fetch/ …2 replies 0 retweets 0 likes -
Replying to @jaffathecake
@jaffathecake guess part of me is also very upset about a promise only API.1 reply 0 retweets 0 likes -
-
Replying to @jaffathecake
@jaffathecake because they force me to work around them. Functions can be converted to promises, implicit catch is hard to revert.1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
@yoshuawuyts why do you need to work around them?1 reply 0 retweets 0 likes -
Replying to @jaffathecake
@jaffathecake implicit catch. Exceptions should bubble up3 replies 0 retweets 0 likes -
Replying to @yoshuawuyts
@yoshuawuyts bubble up to what? Should the page crash?1 reply 0 retweets 0 likes -
Replying to @jaffathecake
@jaffathecake The issue I'm having is that I don't think document.fetch should decide for me if it should or shouldn't.2 replies 0 retweets 0 likes -
Replying to @yoshuawuyts
@yoshuawuyts promise rejections hit the console and soon window events https://code.google.com/p/chromium/issues/detail?id=495801 … - what's missing?3 replies 0 retweets 0 likes
@jaffathecake I take this is not for all rejections? Only unhandled ones? Feels like a lot of noise otherwise.
-
-
Replying to @yoshuawuyts
@yoshuawuyts correct. If a promise rejection is unhandled but then later handled, it'll appear in the console, then it's retracted.0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.