I really like fetch. That said, I still think it's silly that it doesn't reject on statuses between 400 and 600. Literally forced to write a then that checks and throws all the time. It's a shame that ship has sailed. It's still WAY easier to wrap than XHR though.
-
-
What I mean is that: no matter what the default is, you would often need to alter the handling of 404 depending on the design/intentions of the API you are integrating with.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
To me, no representation of a resource found at an endpoint you're expecting a resource should trigger 404, & should be something a dev handle amongst other errors via `catch`. Diff if you're expecting a collection of a subresource of an existing entity since that can be empty.
Thanks. 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.