{"comment":{"url":"https://api.github.com/repos/enmasseio/evejs/comments/9293178","html_url":"https://github.com/enmasseio/evejs/commit/aa78b294c905316239209a0a4c83da92b9e3ecef#commitcomment-9293178","id":9293178,"user":{"login":"AlexDM0","id":5363277,"avatar_url":"https://avatars.githubusercontent.com/u/5363277?v=3","gravatar_id":"","url":"https://api.github.com/users/AlexDM0","html_url":"https://github.com/AlexDM0","followers_url":"https://api.github.com/users/AlexDM0/followers","following_url":"https://api.github.com/users/AlexDM0/following{/other_user}","gists_url":"https://api.github.com/users/AlexDM0/gists{/gist_id}","starred_url":"https://api.github.com/users/AlexDM0/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/AlexDM0/subscriptions","organizations_url":"https://api.github.com/users/AlexDM0/orgs","repos_url":"https://api.github.com/users/AlexDM0/repos","events_url":"https://api.github.com/users/AlexDM0/events{/privacy}","received_events_url":"https://api.github.com/users/AlexDM0/received_events","type":"User","site_admin":false},"position":101,"line":202,"path":"lib/transport/http/HTTPTransport.js","commit_id":"aa78b294c905316239209a0a4c83da92b9e3ecef","created_at":"2015-01-15T08:55:37Z","updated_at":"2015-01-15T08:55:37Z","body":"I think I tried this while setting this up, JSON parse didn't like it when it was a string to begin with. I'd have to double check but I think that's why there's all those checks and catches. \r\n\r\n\r\n\r\n> On 15 jan. 2015, at 09:53, Jos de Jong <notifications@github.com> wrote:\r\n> \r\n> No, just a single, consistent way of serializing what we send.\r\n> \r\n> In this case, if we do a JSON.stringify on the message when it's a string too, a string like foo will be serialized as \"foo\", and an object like {foo:123} will be serialized as {\"foo\":123}. The receiving side can safely do a JSON.parse and gets back the original data type, either a string or an Object.\r\n> \r\n> —\r\n> Reply to this email directly or view it on GitHub.\r\n> "}}