{"comment":{"created_at":"2011-12-02T22:53:03Z","commit_id":"34d2778db0b2cb75ad37d1c4eb014afc056e1772","position":4,"updated_at":"2011-12-02T22:53:03Z","user":{"gravatar_id":"0475975ee298ce15fe5d1ac33960e248","id":188402,"url":"https://api.github.com/users/wfleming","avatar_url":"https://secure.gravatar.com/avatar/0475975ee298ce15fe5d1ac33960e248?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"wfleming"},"body":"Ah. That makes sense: I don't think we need to attach any metadata or anything. I would suggest changing the name of the field, though, if that's the intended purpose. 'name', to me, doesn't feel appropriate for the intended use - currently we use the space in question for author name & branch on commits, but since this is a generic endpoint it could really end up being anything, so I think something closer to the field's presentational function might be better. As I suggested below, 'submessage' or 'caption' seem appropriate to me. Just my humble opinion, though.","line":4,"id":765451,"path":"endpoint.coffee","html_url":"https://github.com/mintdigital/mint-source/commit/34d2778db0#commitcomment-765451","url":"https://api.github.com/repos/mintdigital/mint-source/comments/765451"}}