- From: Domenic Denicola <notifications@github.com>
- Date: Mon, 14 Dec 2015 09:44:29 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
Received on Monday, 14 December 2015 17:44:57 UTC
I think this case is a bit subtle since `res.body` can return `null` so it's a little strange to disallow passing in `null`. Another way to think about it is that `undefined` is supposed to be a default-value triggerer. In this case the default value seems to be ... `null`. And it's weird that you can only set the default value implicitly, not explicitly. It would be a different story if `res.body` returned `undefined` for null body, but it doesn't. (And I think that's probably a good thing.) --- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/178#issuecomment-164506894
Received on Monday, 14 December 2015 17:44:57 UTC