Re: [whatwg/url] Make URLSearchParams' record constructor more flexible (#204)

I agree that the object format is not the best representation for headers, but **if** you're going to support it, then I think you should also support the array values. As I can imagine developers would blindly pass in node header/querystring objects into `URLSearchParams` without realising the formats are not compatible. I think it's just going to be a source of bugs then.
You seem quite opposed to the idea, I don't have that strong feelings towards it so I'd recommend to do away with the object format altogether. No reason to have two ways of doing things, especially if one of those is incompatible with existing solutions.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/pull/204#issuecomment-276710539