- From: Domenic Denicola <domenic@domenicdenicola.com>
- Date: Wed, 25 Jun 2014 15:17:02 +0000
- To: Anne van Kesteren <annevk@annevk.nl>, WHATWG <whatwg@whatwg.org>
- Cc: Jake Archibald <jaffathecake@gmail.com>
Hmm. To clarify, this is in case the server sends you application/x-www-form-urlencoded data, and you want to then get it in a format that can easily become a mutable query string or form data object? If so, neither use case seems like they are worth the convenience method to me. Servers sending data in that format (as opposed to JSON) are pretty rare. And it's even rarer that you want to get the data in that former, then manipulate it before sending it along; usually you would just pass it along as an opaque string. I would rather that the query string parser and the form data parser be exposed by their relevant specs, i.e. people would just use ```js var params = new URLSearchParams(req.body.asText()); var data = new FormData(req.body.asText()); // why doesn't this work currently? ``` I guess a similar argument can be made for `var json = JSON.parse(req.body.asText())`, but that is a much more common use case. Am I wrong?
Received on Wednesday, 25 June 2014 15:17:39 UTC