{"action":"created","issue":{"url":"https://api.github.com/repos/canton7/RestEase/issues/56","repository_url":"https://api.github.com/repos/canton7/RestEase","labels_url":"https://api.github.com/repos/canton7/RestEase/issues/56/labels{/name}","comments_url":"https://api.github.com/repos/canton7/RestEase/issues/56/comments","events_url":"https://api.github.com/repos/canton7/RestEase/issues/56/events","html_url":"https://github.com/canton7/RestEase/issues/56","id":249029585,"number":56,"title":"Support for Stream response","user":{"login":"MaxDeg","id":6094373,"avatar_url":"https://avatars0.githubusercontent.com/u/6094373?v=4","gravatar_id":"","url":"https://api.github.com/users/MaxDeg","html_url":"https://github.com/MaxDeg","followers_url":"https://api.github.com/users/MaxDeg/followers","following_url":"https://api.github.com/users/MaxDeg/following{/other_user}","gists_url":"https://api.github.com/users/MaxDeg/gists{/gist_id}","starred_url":"https://api.github.com/users/MaxDeg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/MaxDeg/subscriptions","organizations_url":"https://api.github.com/users/MaxDeg/orgs","repos_url":"https://api.github.com/users/MaxDeg/repos","events_url":"https://api.github.com/users/MaxDeg/events{/privacy}","received_events_url":"https://api.github.com/users/MaxDeg/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":11,"created_at":"2017-08-09T13:24:37Z","updated_at":"2017-08-11T07:33:46Z","closed_at":null,"body":"Is it possible to support stream response on interface? (I can make the PR)\r\nFor now this kind of method is not supported\r\n```csharp\r\npublic interface I1\r\n{\r\n    [Get(\"/{id}\")]\r\n    Task<Stream> GetContent(string id);\r\n}\r\n```\r\nCould be useful to be able to return directly the response stream without the necessity of exposing the HttpResponseMessage in the interface.\r\n\r\nWhat do you think?"},"comment":{"url":"https://api.github.com/repos/canton7/RestEase/issues/comments/321748123","html_url":"https://github.com/canton7/RestEase/issues/56#issuecomment-321748123","issue_url":"https://api.github.com/repos/canton7/RestEase/issues/56","id":321748123,"user":{"login":"canton7","id":568104,"avatar_url":"https://avatars0.githubusercontent.com/u/568104?v=4","gravatar_id":"","url":"https://api.github.com/users/canton7","html_url":"https://github.com/canton7","followers_url":"https://api.github.com/users/canton7/followers","following_url":"https://api.github.com/users/canton7/following{/other_user}","gists_url":"https://api.github.com/users/canton7/gists{/gist_id}","starred_url":"https://api.github.com/users/canton7/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/canton7/subscriptions","organizations_url":"https://api.github.com/users/canton7/orgs","repos_url":"https://api.github.com/users/canton7/repos","events_url":"https://api.github.com/users/canton7/events{/privacy}","received_events_url":"https://api.github.com/users/canton7/received_events","type":"User","site_admin":false},"created_at":"2017-08-11T07:33:46Z","updated_at":"2017-08-11T07:33:46Z","body":"Fair point, a Lazy would work well. I'm also not happy with how the non-async methods suddenly became blocking in the `Response<T>`, so more work to be done there....\r\n\r\nI think JsonResponseDeserializer is fine. It deserializes JSON responses, and passes through things which aren't JSON. A bare string isn't valid JSON, and so it makes sense that it's the JSON deserializer which decides not to try and deserialize it."}}
{"actor":{"display_login":"canton7"}}