{"action":"opened","issue":{"url":"https://api.github.com/repos/camirmas/grapple/issues/11","repository_url":"https://api.github.com/repos/camirmas/grapple","labels_url":"https://api.github.com/repos/camirmas/grapple/issues/11/labels{/name}","comments_url":"https://api.github.com/repos/camirmas/grapple/issues/11/comments","events_url":"https://api.github.com/repos/camirmas/grapple/issues/11/events","html_url":"https://github.com/camirmas/grapple/issues/11","id":180349284,"number":11,"title":"Support subscription queries via GraphQL","user":{"login":"slurmulon","id":10688625,"avatar_url":"https://avatars.githubusercontent.com/u/10688625?v=3","gravatar_id":"","url":"https://api.github.com/users/slurmulon","html_url":"https://github.com/slurmulon","followers_url":"https://api.github.com/users/slurmulon/followers","following_url":"https://api.github.com/users/slurmulon/following{/other_user}","gists_url":"https://api.github.com/users/slurmulon/gists{/gist_id}","starred_url":"https://api.github.com/users/slurmulon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/slurmulon/subscriptions","organizations_url":"https://api.github.com/users/slurmulon/orgs","repos_url":"https://api.github.com/users/slurmulon/repos","events_url":"https://api.github.com/users/slurmulon/events{/privacy}","received_events_url":"https://api.github.com/users/slurmulon/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/camirmas/grapple/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-09-30T16:40:01Z","updated_at":"2016-09-30T16:40:01Z","closed_at":null,"body":"Instead of only allowing users to subscribe to simple and limited keys (like __MODULE__.name), we should allow them to apply a GraphQL query.\n\nThis feature would let users have fine grained control over when they receive a hook broadcast (topic refinement) and possibly what data they want to receive in the broadcast - perhaps they only want a specific subset of data, or need the data to be marshalled into a format that works with their API bit easier. Lots of people use generic serializers that can get easily tripped up when working with unusually shaped data (they are of course poorly written, but we should still help them out, I think anyways)"}}
{"actor":{"display_login":"slurmulon"}}