{"action":"closed","issue":{"url":"https://api.github.com/repos/abelsilva/swaggerwcf/issues/43","repository_url":"https://api.github.com/repos/abelsilva/swaggerwcf","labels_url":"https://api.github.com/repos/abelsilva/swaggerwcf/issues/43/labels{/name}","comments_url":"https://api.github.com/repos/abelsilva/swaggerwcf/issues/43/comments","events_url":"https://api.github.com/repos/abelsilva/swaggerwcf/issues/43/events","html_url":"https://github.com/abelsilva/swaggerwcf/issues/43","id":181926632,"number":43,"title":"change /swagger.json UriTemplate or allow it to be configurable","user":{"login":"amelialaundy","id":7699279,"avatar_url":"https://avatars.githubusercontent.com/u/7699279?v=3","gravatar_id":"","url":"https://api.github.com/users/amelialaundy","html_url":"https://github.com/amelialaundy","followers_url":"https://api.github.com/users/amelialaundy/followers","following_url":"https://api.github.com/users/amelialaundy/following{/other_user}","gists_url":"https://api.github.com/users/amelialaundy/gists{/gist_id}","starred_url":"https://api.github.com/users/amelialaundy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/amelialaundy/subscriptions","organizations_url":"https://api.github.com/users/amelialaundy/orgs","repos_url":"https://api.github.com/users/amelialaundy/repos","events_url":"https://api.github.com/users/amelialaundy/events{/privacy}","received_events_url":"https://api.github.com/users/amelialaundy/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-10-10T02:01:04Z","updated_at":"2016-10-17T00:52:44Z","closed_at":"2016-10-17T00:52:44Z","body":"Hey Abel, \r\nI came across your implementation of Swagger for WCF and have managed to get it working on our solution (we have a handrolled solution for documentation at the moment and need to move towards swagger).\r\n\r\nThe only issue I came across is that the SwaggerWcfEndpoint implementation uses “/swagger.json” as the UriTemplate and I finally realised that this was what was causing the swagger output to be inaccessible in our API. \r\nAs soon as I got your code running inside our solution and could debug through it I changed the URL to “/swagger” and it worked perfectly. (we actually can't access the UI component hosted at the other endpoint in ISwaggerWcfEndpoint.cs but don't need to use it so it's not causing an issue).\r\n\r\nI believe this is down to how WCF routing can pick up specific urls or ignore others, I did find an article that semi explained it but I seem to have lost it.\r\n\r\nSo I’m just wondering whether this is something you would consider either changing (/swagger.json) or to allow it to be configurable by the user ( happy to try and solve this and do a PR)?\r\n"}}
{"actor":{"display_login":"abelsilva"}}