{"action":"opened","issue":{"url":"https://api.github.com/repos/pol-is/issues/issues/6","repository_url":"https://api.github.com/repos/pol-is/issues","labels_url":"https://api.github.com/repos/pol-is/issues/issues/6/labels{/name}","comments_url":"https://api.github.com/repos/pol-is/issues/issues/6/comments","events_url":"https://api.github.com/repos/pol-is/issues/issues/6/events","html_url":"https://github.com/pol-is/issues/issues/6","id":193207061,"number":6,"title":"Make API response object keys consistent","user":{"login":"patcon","id":305339,"avatar_url":"https://avatars.githubusercontent.com/u/305339?v=3","gravatar_id":"","url":"https://api.github.com/users/patcon","html_url":"https://github.com/patcon","followers_url":"https://api.github.com/users/patcon/followers","following_url":"https://api.github.com/users/patcon/following{/other_user}","gists_url":"https://api.github.com/users/patcon/gists{/gist_id}","starred_url":"https://api.github.com/users/patcon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/patcon/subscriptions","organizations_url":"https://api.github.com/users/patcon/orgs","repos_url":"https://api.github.com/users/patcon/repos","events_url":"https://api.github.com/users/patcon/events{/privacy}","received_events_url":"https://api.github.com/users/patcon/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-12-02T20:11:09Z","updated_at":"2016-12-02T20:11:09Z","closed_at":null,"body":"First off, I really appreciate that you guys are adding new API features for the community! Just wanted to put that out there ;)\r\n\r\nI'm in the process of documenting the API in swagger format:\r\nhttp://petstore.swagger.io/?url=https://patcon.github.io/polis-api-spec/swagger.json#/\r\n\r\nOne (hopefully) small request to simplify documentation and maintain RESTfulness (even though that's a fuzzy term): Could you work toward responses where (when possible) fields don't appear and disappear based on a param flags? In my understanding, it's best to just include these all the time, but we can define them as being \"nullable\" and in the field description, we can point out that flag so-and-so makes this return a non-null value.\r\n\r\nAnyhow, thanks! (This is particularly in response to `want_voteCountUnique` on `GET /conversations`, but I know i've seen it crop up elsewhere while I've been sorting through things :) [[Context]](https://meta-pol-is.slack.com/archives/software-development/p1480552880000033)"}}
{"actor":{"display_login":"patcon"}}