{"action":"created","issue":{"url":"https://api.github.com/repos/rejectedsoftware/vibe.d/issues/1070","labels_url":"https://api.github.com/repos/rejectedsoftware/vibe.d/issues/1070/labels{/name}","comments_url":"https://api.github.com/repos/rejectedsoftware/vibe.d/issues/1070/comments","events_url":"https://api.github.com/repos/rejectedsoftware/vibe.d/issues/1070/events","html_url":"https://github.com/rejectedsoftware/vibe.d/issues/1070","id":68541199,"number":1070,"title":"Generate Swagger API","user":{"login":"Zalastax","id":908496,"avatar_url":"https://avatars.githubusercontent.com/u/908496?v=3","gravatar_id":"","url":"https://api.github.com/users/Zalastax","html_url":"https://github.com/Zalastax","followers_url":"https://api.github.com/users/Zalastax/followers","following_url":"https://api.github.com/users/Zalastax/following{/other_user}","gists_url":"https://api.github.com/users/Zalastax/gists{/gist_id}","starred_url":"https://api.github.com/users/Zalastax/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Zalastax/subscriptions","organizations_url":"https://api.github.com/users/Zalastax/orgs","repos_url":"https://api.github.com/users/Zalastax/repos","events_url":"https://api.github.com/users/Zalastax/events{/privacy}","received_events_url":"https://api.github.com/users/Zalastax/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":21,"created_at":"2015-04-15T01:19:20Z","updated_at":"2015-04-15T13:55:17Z","closed_at":null,"body":"[Swagger](http://swagger.io/) is the best way I know to visualize your REST interface. It works by generating a JSON-document describing the API. The Swagger UI reads this document and generates a documentation page where you can read about the API functions, required schemas, and try out valid requests.\r\nYou have a REST interface generator so this should be quite straightforward to implement. I don't think it could work for freestanding routing without changes since the information about required types is never available to the router. The REST generator seem to be given an overhaul https://github.com/rejectedsoftware/vibe.d/issues/1040 so should I wait with looking into this?"},"comment":{"url":"https://api.github.com/repos/rejectedsoftware/vibe.d/issues/comments/93410352","html_url":"https://github.com/rejectedsoftware/vibe.d/issues/1070#issuecomment-93410352","issue_url":"https://api.github.com/repos/rejectedsoftware/vibe.d/issues/1070","id":93410352,"user":{"login":"rikkimax","id":992755,"avatar_url":"https://avatars.githubusercontent.com/u/992755?v=3","gravatar_id":"","url":"https://api.github.com/users/rikkimax","html_url":"https://github.com/rikkimax","followers_url":"https://api.github.com/users/rikkimax/followers","following_url":"https://api.github.com/users/rikkimax/following{/other_user}","gists_url":"https://api.github.com/users/rikkimax/gists{/gist_id}","starred_url":"https://api.github.com/users/rikkimax/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rikkimax/subscriptions","organizations_url":"https://api.github.com/users/rikkimax/orgs","repos_url":"https://api.github.com/users/rikkimax/repos","events_url":"https://api.github.com/users/rikkimax/events{/privacy}","received_events_url":"https://api.github.com/users/rikkimax/received_events","type":"User","site_admin":false},"created_at":"2015-04-15T13:55:17Z","updated_at":"2015-04-15T13:55:17Z","body":"@s-ludwig I'm thinking of a 10 year plan here. So things like language changes are not out of the question to make it nice to the end developer. After all, how can we prioritise what is important now, if we have no clue where we are going."}}