{"action":"created","issue":{"url":"https://api.github.com/repos/lagom/lagom/issues/488","repository_url":"https://api.github.com/repos/lagom/lagom","labels_url":"https://api.github.com/repos/lagom/lagom/issues/488/labels{/name}","comments_url":"https://api.github.com/repos/lagom/lagom/issues/488/comments","events_url":"https://api.github.com/repos/lagom/lagom/issues/488/events","html_url":"https://github.com/lagom/lagom/issues/488","id":208293403,"number":488,"title":"Support Option/Optional response message being encoded as 404 not found","user":{"login":"jroper","id":105833,"avatar_url":"https://avatars.githubusercontent.com/u/105833?v=3","gravatar_id":"","url":"https://api.github.com/users/jroper","html_url":"https://github.com/jroper","followers_url":"https://api.github.com/users/jroper/followers","following_url":"https://api.github.com/users/jroper/following{/other_user}","gists_url":"https://api.github.com/users/jroper/gists{/gist_id}","starred_url":"https://api.github.com/users/jroper/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jroper/subscriptions","organizations_url":"https://api.github.com/users/jroper/orgs","repos_url":"https://api.github.com/users/jroper/repos","events_url":"https://api.github.com/users/jroper/events{/privacy}","received_events_url":"https://api.github.com/users/jroper/received_events","type":"User","site_admin":false},"labels":[{"id":330385909,"url":"https://api.github.com/repos/lagom/lagom/labels/enhancement","name":"enhancement","color":"84b6eb","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":10,"created_at":"2017-02-17T00:25:22Z","updated_at":"2017-02-20T00:13:24Z","closed_at":null,"body":"It would be nice if you could declare a response message to be an Option/Optional, and as such, when None/empty was returned, the API would return a 404 status code.\r\n\r\nThere are two ways that this could be implemented that I see:\r\n\r\n1. Add specific knowledge of option/optional serializers to the implementation of the server/client, to implement this.\r\n2. Add a generic way for serializers to modify and read request/response headers, possibly in a similar way to the way ServiceCalls handle request/repsonse headers. This approach would allow other similar requirements, like returning Created objects with a location field, that automatically get serialized as a 201 response code with a location header, etc etc."},"comment":{"url":"https://api.github.com/repos/lagom/lagom/issues/comments/280961597","html_url":"https://github.com/lagom/lagom/issues/488#issuecomment-280961597","issue_url":"https://api.github.com/repos/lagom/lagom/issues/488","id":280961597,"user":{"login":"jroper","id":105833,"avatar_url":"https://avatars.githubusercontent.com/u/105833?v=3","gravatar_id":"","url":"https://api.github.com/users/jroper","html_url":"https://github.com/jroper","followers_url":"https://api.github.com/users/jroper/followers","following_url":"https://api.github.com/users/jroper/following{/other_user}","gists_url":"https://api.github.com/users/jroper/gists{/gist_id}","starred_url":"https://api.github.com/users/jroper/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jroper/subscriptions","organizations_url":"https://api.github.com/users/jroper/orgs","repos_url":"https://api.github.com/users/jroper/repos","events_url":"https://api.github.com/users/jroper/events{/privacy}","received_events_url":"https://api.github.com/users/jroper/received_events","type":"User","site_admin":false},"created_at":"2017-02-20T00:13:24Z","updated_at":"2017-02-20T00:13:24Z","body":"@viktorklang given that we only support one transport currently, it's not really that well documented or talked about, at least not in that light, but the APIs and necessary semantics are all there to be able to define message serializers that use different protocols based on a variety of different conditions."}}
{"actor":{"display_login":"jroper"}}