- From: Cole Hansen <notifications@github.com>
- Date: Wed, 12 Jul 2017 18:34:06 +0000 (UTC)
- To: whatwg/url <url@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/url/issues/335@github.com>
The specification for URLSearchParams currently reads that delete should delete all pairs that have the supplied key. I think the ability to delete a specific key value pair should be added. For example: ```js let url = new URLSearchParams("key1=value1&key1=value1a&key2=value2"); url.delete("key1","value1"); url.toString(); // key1=value1a&key2=value2 ``` A use case for this is faceted searching. Say the user has selected three keys to facet with. Example url: ```http://example.com/?q=searchTerms&facet.category=selection1&facet.category=selection2&facet.category=selection3```. Now the user wants to clear only selection2 from their search. While it wouldn't be too difficult to use the current methods to obtain the desired output above (getAll the given key, delete all pairs with the given key, iterate over the getAll result adding back everything but the one pair), I think it goes against the goal of the URLSearchParams class as I understand it. It seems URLSearchParams tries to abstract away the string filtering and concatenations that were required for query params before. The workaround falls back into that extra manipulation approach. I think that any of the following changes would solve this. 1) Allow a second optional argument to be passed to delete that would specify the value of which key-value to delete if there were multiple key-value pairs with the given key. Example: See above. 2) Change the current definition of delete to require two arguments, a key and a value. The method would then delete the supplied key-value pair, if it exists. Introduce a new method, deleteAll, that behaves how delete does currently. This would follow the pattern of having both get and getAll methods. ```js let url = new URLSearchParams("key1=value1&key1=value1a&key2=value2&key2=value2b"); url.delete("key1","value1"); url.toString(); // key1=value1a&key2=value2&key2=value2b url.deleteAll("key2"); url.toString(); // key1=value1a ``` For both options, in cases where there are repeats of the same key-value pair, all instances would be deleted. Example: ```js let url = new URLSearchParams("key1=value1&key1=value1&key2=value2"); url.delete("key1","value1"); url.toString(); // key2=value2 ``` While I am more of a fan of option 2 because it lines up closer to the get/getAll methods, it requires a backwards incompatible change. Therefore, it would probably be best to go the route of option 1. (Arguably, a third option could be to keep 1 argument delete the same, introduce deleteAll and two argument delete, but is probably extra and unnecessary.) What are other people's thoughts? -- 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/issues/335
Received on Wednesday, 12 July 2017 18:34:37 UTC