{"action":"created","issue":{"url":"https://api.github.com/repos/artemis-nerds/protocol-docs/issues/50","repository_url":"https://api.github.com/repos/artemis-nerds/protocol-docs","labels_url":"https://api.github.com/repos/artemis-nerds/protocol-docs/issues/50/labels{/name}","comments_url":"https://api.github.com/repos/artemis-nerds/protocol-docs/issues/50/comments","events_url":"https://api.github.com/repos/artemis-nerds/protocol-docs/issues/50/events","html_url":"https://github.com/artemis-nerds/protocol-docs/issues/50","id":176286379,"number":50,"title":"Convert protocol description to structured data format, generate everything from that","user":{"login":"chrivers","id":644439,"avatar_url":"https://avatars.githubusercontent.com/u/644439?v=3","gravatar_id":"","url":"https://api.github.com/users/chrivers","html_url":"https://github.com/chrivers","followers_url":"https://api.github.com/users/chrivers/followers","following_url":"https://api.github.com/users/chrivers/following{/other_user}","gists_url":"https://api.github.com/users/chrivers/gists{/gist_id}","starred_url":"https://api.github.com/users/chrivers/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/chrivers/subscriptions","organizations_url":"https://api.github.com/users/chrivers/orgs","repos_url":"https://api.github.com/users/chrivers/repos","events_url":"https://api.github.com/users/chrivers/events{/privacy}","received_events_url":"https://api.github.com/users/chrivers/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":10,"created_at":"2016-09-12T03:10:43Z","updated_at":"2016-09-13T16:09:36Z","closed_at":null,"body":""},"comment":{"url":"https://api.github.com/repos/artemis-nerds/protocol-docs/issues/comments/246734745","html_url":"https://github.com/artemis-nerds/protocol-docs/issues/50#issuecomment-246734745","issue_url":"https://api.github.com/repos/artemis-nerds/protocol-docs/issues/50","id":246734745,"user":{"login":"rjwut","id":5790951,"avatar_url":"https://avatars.githubusercontent.com/u/5790951?v=3","gravatar_id":"","url":"https://api.github.com/users/rjwut","html_url":"https://github.com/rjwut","followers_url":"https://api.github.com/users/rjwut/followers","following_url":"https://api.github.com/users/rjwut/following{/other_user}","gists_url":"https://api.github.com/users/rjwut/gists{/gist_id}","starred_url":"https://api.github.com/users/rjwut/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rjwut/subscriptions","organizations_url":"https://api.github.com/users/rjwut/orgs","repos_url":"https://api.github.com/users/rjwut/repos","events_url":"https://api.github.com/users/rjwut/events{/privacy}","received_events_url":"https://api.github.com/users/rjwut/received_events","type":"User","site_admin":false},"created_at":"2016-09-13T16:09:36Z","updated_at":"2016-09-13T16:09:36Z","body":"I think that if we can make an existing data format work without too much difficulty, we should, so as not not have to maintain a custom parser. Of what's been shown so far, I like the YAML example the best. While I'm a fan of JSON and generally not a fan of syntactically-significant whitespace, I can see why YAML might be a good fit for this project. I was experimenting with a JSON implementation just to see what it would look like, but I agree that the anchor and tagging features of YAML would be useful for this. I'm not sure that I like using comments for descriptions; I get that it makes sense in that they are intended for humans and therefore not useful to code generators, but the documentation generator will need it, so it's actually data, not just a comment. Would a YAML parser throw the comments away, or are they accessible in the resulting data structure?"}}
{"actor":{"display_login":"rjwut"}}