Re: [fetch] Option to require response.ok (#103)

I don't think this sugar is worth it. `{ requiredStatus: ok }` saves very little characters over `.then(res => { if (!res.ok) throw new TypeError() })`, even with an informative message. And as you note, it spreads to more and more of the API.

People just need to realize the underlying mental model is that fetch returns responses, and responses can be not-OK, and they should handle that.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/103#issuecomment-128031313