{"action":"created","issue":{"url":"https://api.github.com/repos/haxetink/tink_web/issues/7","repository_url":"https://api.github.com/repos/haxetink/tink_web","labels_url":"https://api.github.com/repos/haxetink/tink_web/issues/7/labels{/name}","comments_url":"https://api.github.com/repos/haxetink/tink_web/issues/7/comments","events_url":"https://api.github.com/repos/haxetink/tink_web/issues/7/events","html_url":"https://github.com/haxetink/tink_web/issues/7","id":158884358,"number":7,"title":"Export routing information","user":{"login":"skial","id":379926,"avatar_url":"https://avatars1.githubusercontent.com/u/379926?v=3","gravatar_id":"","url":"https://api.github.com/users/skial","html_url":"https://github.com/skial","followers_url":"https://api.github.com/users/skial/followers","following_url":"https://api.github.com/users/skial/following{/other_user}","gists_url":"https://api.github.com/users/skial/gists{/gist_id}","starred_url":"https://api.github.com/users/skial/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/skial/subscriptions","organizations_url":"https://api.github.com/users/skial/orgs","repos_url":"https://api.github.com/users/skial/repos","events_url":"https://api.github.com/users/skial/events{/privacy}","received_events_url":"https://api.github.com/users/skial/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2016-06-07T09:59:28Z","updated_at":"2017-06-20T05:35:19Z","closed_at":null,"body":"I've been experimenting with the `tink_*`, web libraries and aws lambda and have a rough `tink_http` container implementation that works targeting the node runtime.\n\nTo have aws lambda working via http, you have to use aws api gateway which uses, imo, an odd request/response integration _\"frontend\"_ to your aws lambda function.\n\nThis requires you to specify a path segment, which http method it accepts, the expected mime type and more.\n\nAs `tink_web` has the ability to access the majority of the http info already from your routes, would there be interest in having `tink_web` export the info to json or some other format, like openapi?\n"},"comment":{"url":"https://api.github.com/repos/haxetink/tink_web/issues/comments/309649577","html_url":"https://github.com/haxetink/tink_web/issues/7#issuecomment-309649577","issue_url":"https://api.github.com/repos/haxetink/tink_web/issues/7","id":309649577,"user":{"login":"kevinresol","id":1103788,"avatar_url":"https://avatars3.githubusercontent.com/u/1103788?v=3","gravatar_id":"","url":"https://api.github.com/users/kevinresol","html_url":"https://github.com/kevinresol","followers_url":"https://api.github.com/users/kevinresol/followers","following_url":"https://api.github.com/users/kevinresol/following{/other_user}","gists_url":"https://api.github.com/users/kevinresol/gists{/gist_id}","starred_url":"https://api.github.com/users/kevinresol/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kevinresol/subscriptions","organizations_url":"https://api.github.com/users/kevinresol/orgs","repos_url":"https://api.github.com/users/kevinresol/repos","events_url":"https://api.github.com/users/kevinresol/events{/privacy}","received_events_url":"https://api.github.com/users/kevinresol/received_events","type":"User","site_admin":false},"created_at":"2017-06-20T05:35:19Z","updated_at":"2017-06-20T05:35:19Z","body":"Maybe AWS has changed the API or something. Now it doesn't need a manual mapping template. Simply \"use lambda proxy integration\"\r\n\r\n![image](https://user-images.githubusercontent.com/1103788/27318022-9fefa700-55bc-11e7-9a97-b4a05bfe0613.png)\r\n\r\n**Quick links:**\r\n- [Data format doc](http://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-set-up-simple-proxy.html#api-gateway-simple-proxy-for-lambda-input-format)\r\n- [Container implementation]( https://github.com/kevinresol/tink_http/blob/aws_lambda_node/src/tink/http/containers/AwsLambdaNodeContainer.hx)\r\n\r\n**A few known limitations:**\r\n- duplicated query params not supported (because it is represented as key-value object)\r\n- duplicated headers not supported (because it is represented as key-value object)\r\n- streaming not supported (because the whole request/response is encoded into a json)\r\n- need to distinguish the response type between plain-text or binary. Because if it is binary it has to be base64 encoded\r\n"}}
{"actor":{"display_login":"kevinresol"}}