{"action":"created","issue":{"url":"https://api.github.com/repos/whatwg/fetch/issues/56","repository_url":"https://api.github.com/repos/whatwg/fetch","labels_url":"https://api.github.com/repos/whatwg/fetch/issues/56/labels{/name}","comments_url":"https://api.github.com/repos/whatwg/fetch/issues/56/comments","events_url":"https://api.github.com/repos/whatwg/fetch/issues/56/events","html_url":"https://github.com/whatwg/fetch/issues/56","id":81520696,"number":56,"title":"Document usage for GET requests with URI parameters","user":{"login":"theefer","id":36964,"avatar_url":"https://avatars.githubusercontent.com/u/36964?v=3","gravatar_id":"","url":"https://api.github.com/users/theefer","html_url":"https://github.com/theefer","followers_url":"https://api.github.com/users/theefer/followers","following_url":"https://api.github.com/users/theefer/following{/other_user}","gists_url":"https://api.github.com/users/theefer/gists{/gist_id}","starred_url":"https://api.github.com/users/theefer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/theefer/subscriptions","organizations_url":"https://api.github.com/users/theefer/orgs","repos_url":"https://api.github.com/users/theefer/repos","events_url":"https://api.github.com/users/theefer/events{/privacy}","received_events_url":"https://api.github.com/users/theefer/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-05-27T16:32:05Z","updated_at":"2016-05-30T03:02:58Z","closed_at":"2015-07-16T12:42:03Z","body":"The spec does not document any way to specify GET query parameters (e.g. `search?q=unicorns&limit=10&foobar`) for a request. GET is the most common case but in practice, query parameters may be used with any HTTP method.\r\n\r\nAs I understand, the way to do this is using  [`URLSearchParams`](https://url.spec.whatwg.org/#urlsearchparams) from the URL spec. It would be good to provide a clearer view of how these two APIs fit together, especially as query strings are often supported directly by the high-level XHR APIs that `fetch` is meant to replace (e.g. jQuery.ajax or reqwest), often as a `data` option for example.\r\n\r\nIn general, it feels like it would be really great to have a boilerplate-free way to use only native web APIs to do such common things as passing URI parameters.\r\n\r\nSee also [this Twitter thread](https://twitter.com/tabatkins/status/603564595391762432)."},"comment":{"url":"https://api.github.com/repos/whatwg/fetch/issues/comments/222402921","html_url":"https://github.com/whatwg/fetch/issues/56#issuecomment-222402921","issue_url":"https://api.github.com/repos/whatwg/fetch/issues/56","id":222402921,"user":{"login":"domenic","id":617481,"avatar_url":"https://avatars.githubusercontent.com/u/617481?v=3","gravatar_id":"","url":"https://api.github.com/users/domenic","html_url":"https://github.com/domenic","followers_url":"https://api.github.com/users/domenic/followers","following_url":"https://api.github.com/users/domenic/following{/other_user}","gists_url":"https://api.github.com/users/domenic/gists{/gist_id}","starred_url":"https://api.github.com/users/domenic/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/domenic/subscriptions","organizations_url":"https://api.github.com/users/domenic/orgs","repos_url":"https://api.github.com/users/domenic/repos","events_url":"https://api.github.com/users/domenic/events{/privacy}","received_events_url":"https://api.github.com/users/domenic/received_events","type":"User","site_admin":false},"created_at":"2016-05-30T03:02:58Z","updated_at":"2016-05-30T03:02:58Z","body":"See the last three comments prior to yours."}}
{"actor":{"display_login":"domenic"}}