{"action":"created","issue":{"url":"https://api.github.com/repos/reactjs/react-router/issues/3707","repository_url":"https://api.github.com/repos/reactjs/react-router","labels_url":"https://api.github.com/repos/reactjs/react-router/issues/3707/labels{/name}","comments_url":"https://api.github.com/repos/reactjs/react-router/issues/3707/comments","events_url":"https://api.github.com/repos/reactjs/react-router/issues/3707/events","html_url":"https://github.com/reactjs/react-router/issues/3707","id":169634200,"number":3707,"title":"Add \"props\" as an attribute when configuring a Route","user":{"login":"atrauzzi","id":115199,"avatar_url":"https://avatars.githubusercontent.com/u/115199?v=3","gravatar_id":"","url":"https://api.github.com/users/atrauzzi","html_url":"https://github.com/atrauzzi","followers_url":"https://api.github.com/users/atrauzzi/followers","following_url":"https://api.github.com/users/atrauzzi/following{/other_user}","gists_url":"https://api.github.com/users/atrauzzi/gists{/gist_id}","starred_url":"https://api.github.com/users/atrauzzi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/atrauzzi/subscriptions","organizations_url":"https://api.github.com/users/atrauzzi/orgs","repos_url":"https://api.github.com/users/atrauzzi/repos","events_url":"https://api.github.com/users/atrauzzi/events{/privacy}","received_events_url":"https://api.github.com/users/atrauzzi/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-08-05T15:32:26Z","updated_at":"2016-08-05T15:57:15Z","closed_at":"2016-08-05T15:57:15Z","body":"Plain and simple.  Whatever gets passed in here is like as if they were defined as props on the routed component itself.\r\n\r\nReason: My components shouldn't need to be aware of react router conventions just to be passed parameters from wherever they're being called.\r\n\r\nExample:\r\n\r\n```\r\n<Router>\r\n    <Route path=\"/some/path\" props={myBagOfData} component={UnawareOfReactRouter} />\r\n</Router>\r\n```\r\n\r\nCan't call it props?  Call it `passthroughProps`, the name doesn't matter.  The concept here is that it needs to be easier to preserve standard react conventions without creating a two way coupling between routed components and react-router.  Which is what happens when you make the expectation that components now have to access `this.props.route` to get at any values."},"comment":{"url":"https://api.github.com/repos/reactjs/react-router/issues/comments/237889396","html_url":"https://github.com/reactjs/react-router/issues/3707#issuecomment-237889396","issue_url":"https://api.github.com/repos/reactjs/react-router/issues/3707","id":237889396,"user":{"login":"taion","id":3112159,"avatar_url":"https://avatars.githubusercontent.com/u/3112159?v=3","gravatar_id":"","url":"https://api.github.com/users/taion","html_url":"https://github.com/taion","followers_url":"https://api.github.com/users/taion/followers","following_url":"https://api.github.com/users/taion/following{/other_user}","gists_url":"https://api.github.com/users/taion/gists{/gist_id}","starred_url":"https://api.github.com/users/taion/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/taion/subscriptions","organizations_url":"https://api.github.com/users/taion/orgs","repos_url":"https://api.github.com/users/taion/repos","events_url":"https://api.github.com/users/taion/events{/privacy}","received_events_url":"https://api.github.com/users/taion/received_events","type":"User","site_admin":false},"created_at":"2016-08-05T15:57:15Z","updated_at":"2016-08-05T15:57:15Z","body":"You can trivially build an HoC that spreads the properties of `this.props.route` into the child's props. You can even use a custom route component that automatically applies the HoC.\r\n\r\nI don't think it makes sense to explicitly bring this functionality into the router core."}}
{"actor":{"display_login":"taion"}}