{"action":"created","issue":{"url":"https://api.github.com/repos/haskell-servant/servant/issues/12","labels_url":"https://api.github.com/repos/haskell-servant/servant/issues/12/labels{/name}","comments_url":"https://api.github.com/repos/haskell-servant/servant/issues/12/comments","events_url":"https://api.github.com/repos/haskell-servant/servant/issues/12/events","html_url":"https://github.com/haskell-servant/servant/issues/12","id":58181143,"number":12,"title":"Vote: Naming convention for content-type-aware combinators","user":{"login":"alpmestan","id":119323,"avatar_url":"https://avatars.githubusercontent.com/u/119323?v=3","gravatar_id":"","url":"https://api.github.com/users/alpmestan","html_url":"https://github.com/alpmestan","followers_url":"https://api.github.com/users/alpmestan/followers","following_url":"https://api.github.com/users/alpmestan/following{/other_user}","gists_url":"https://api.github.com/users/alpmestan/gists{/gist_id}","starred_url":"https://api.github.com/users/alpmestan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/alpmestan/subscriptions","organizations_url":"https://api.github.com/users/alpmestan/orgs","repos_url":"https://api.github.com/users/alpmestan/repos","events_url":"https://api.github.com/users/alpmestan/events{/privacy}","received_events_url":"https://api.github.com/users/alpmestan/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-02-19T08:47:21Z","updated_at":"2015-02-20T16:34:24Z","closed_at":null,"body":"Hi folks,\r\n\r\nThere's been a decent amount of work on all the servant libraries since the 0.2 release, among which is a clean and extensible support for content-types.\r\n\r\nMost of the discussion so far about this resides [here](https://github.com/haskell-servant/servant-server/pull/13).\r\n\r\nWe're basically wondering what you, users and fellow servant developers, would prefer:\r\n\r\n1) Keep `Get`, `Post` and friends as the names for the JSON-only endpoints, and have the combinators that take the list of supported content types be named with a final prime (`'`), as in `Get'`, `Post'`, etc. This would probably have the benefit of not breaking any existing code.\r\n2) The reverse: have `Get`, `Post` and friends be the combinators that take a type level list of supported content types, and have `Get'`, `Post'` etc be the simple JSON-only versions.\r\n3) Some other naming convention..?\r\n\r\nThe discussion linked above contains \"sample code\" to give you an idea of what each would look like.\r\n\r\nPlease express your vote in a comment to this issue here, and within a week or two we'll see what naming convention is preferred and we'll just go with that one.\r\n\r\nThanks in advance folks."},"comment":{"url":"https://api.github.com/repos/haskell-servant/servant/issues/comments/75268301","html_url":"https://github.com/haskell-servant/servant/issues/12#issuecomment-75268301","issue_url":"https://api.github.com/repos/haskell-servant/servant/issues/12","id":75268301,"user":{"login":"seubert","id":1221550,"avatar_url":"https://avatars.githubusercontent.com/u/1221550?v=3","gravatar_id":"","url":"https://api.github.com/users/seubert","html_url":"https://github.com/seubert","followers_url":"https://api.github.com/users/seubert/followers","following_url":"https://api.github.com/users/seubert/following{/other_user}","gists_url":"https://api.github.com/users/seubert/gists{/gist_id}","starred_url":"https://api.github.com/users/seubert/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/seubert/subscriptions","organizations_url":"https://api.github.com/users/seubert/orgs","repos_url":"https://api.github.com/users/seubert/repos","events_url":"https://api.github.com/users/seubert/events{/privacy}","received_events_url":"https://api.github.com/users/seubert/received_events","type":"User","site_admin":false},"created_at":"2015-02-20T16:34:24Z","updated_at":"2015-02-20T16:34:24Z","body":"I also waffled on this a bit but I think 2 is best in the long run. It gives a sensible pseudo-default but also contains powerful flexibility."}}