{"action":"created","issue":{"url":"https://api.github.com/repos/emberjs/rfcs/issues/36","labels_url":"https://api.github.com/repos/emberjs/rfcs/issues/36/labels{/name}","comments_url":"https://api.github.com/repos/emberjs/rfcs/issues/36/comments","events_url":"https://api.github.com/repos/emberjs/rfcs/issues/36/events","html_url":"https://github.com/emberjs/rfcs/pull/36","id":58681030,"number":36,"title":"RFC: Optional Segments in Routing","user":{"login":"SlexAxton","id":96554,"avatar_url":"https://avatars.githubusercontent.com/u/96554?v=3","gravatar_id":"","url":"https://api.github.com/users/SlexAxton","html_url":"https://github.com/SlexAxton","followers_url":"https://api.github.com/users/SlexAxton/followers","following_url":"https://api.github.com/users/SlexAxton/following{/other_user}","gists_url":"https://api.github.com/users/SlexAxton/gists{/gist_id}","starred_url":"https://api.github.com/users/SlexAxton/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SlexAxton/subscriptions","organizations_url":"https://api.github.com/users/SlexAxton/orgs","repos_url":"https://api.github.com/users/SlexAxton/repos","events_url":"https://api.github.com/users/SlexAxton/events{/privacy}","received_events_url":"https://api.github.com/users/SlexAxton/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-02-24T01:39:22Z","updated_at":"2015-02-24T15:42:43Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/emberjs/rfcs/pulls/36","html_url":"https://github.com/emberjs/rfcs/pull/36","diff_url":"https://github.com/emberjs/rfcs/pull/36.diff","patch_url":"https://github.com/emberjs/rfcs/pull/36.patch"},"body":"Hi Embereños!\r\n\r\n[RFC](https://github.com/stripe/ember-rfcs/blob/stripe-optional-route-segments/active/0000-optional-route-segments.md)\r\n\r\nWe here at Stripe on the front-end team ( @michelle / @danwang / @slexaxton ) have been working on an RFC for implementing a feature we'd like in our app. We think it's fairly generic, but have hopefully explained our specific use-case as well.\r\n\r\nWe'd be happy to implement entirely or help implement this feature as a Pull Request (likely to a mix of Ember/RouteRecognizer/Router.js) if there is agreement that it should exist."},"comment":{"url":"https://api.github.com/repos/emberjs/rfcs/issues/comments/75780233","html_url":"https://github.com/emberjs/rfcs/pull/36#issuecomment-75780233","issue_url":"https://api.github.com/repos/emberjs/rfcs/issues/36","id":75780233,"user":{"login":"kieran","id":3444,"avatar_url":"https://avatars.githubusercontent.com/u/3444?v=3","gravatar_id":"","url":"https://api.github.com/users/kieran","html_url":"https://github.com/kieran","followers_url":"https://api.github.com/users/kieran/followers","following_url":"https://api.github.com/users/kieran/following{/other_user}","gists_url":"https://api.github.com/users/kieran/gists{/gist_id}","starred_url":"https://api.github.com/users/kieran/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kieran/subscriptions","organizations_url":"https://api.github.com/users/kieran/orgs","repos_url":"https://api.github.com/users/kieran/repos","events_url":"https://api.github.com/users/kieran/events{/privacy}","received_events_url":"https://api.github.com/users/kieran/received_events","type":"User","site_admin":false},"created_at":"2015-02-24T15:42:43Z","updated_at":"2015-02-24T15:42:43Z","body":"I think the gist of it is around trying to maintain a clear mapping between states and routes, while pulling the route definitions out into a separate file.\r\n\r\nThere are quite a few discussions on http://discuss.emberjs.com around nested routes, probably with much better explanations than I can offer ;-)"}}