{"action":"closed","issue":{"url":"https://api.github.com/repos/rackt/react-router/issues/1922","labels_url":"https://api.github.com/repos/rackt/react-router/issues/1922/labels{/name}","comments_url":"https://api.github.com/repos/rackt/react-router/issues/1922/comments","events_url":"https://api.github.com/repos/rackt/react-router/issues/1922/events","html_url":"https://github.com/rackt/react-router/issues/1922","id":106273848,"number":1922,"title":"Accessing route params from a component.","user":{"login":"poeticninja","id":1514196,"avatar_url":"https://avatars.githubusercontent.com/u/1514196?v=3","gravatar_id":"","url":"https://api.github.com/users/poeticninja","html_url":"https://github.com/poeticninja","followers_url":"https://api.github.com/users/poeticninja/followers","following_url":"https://api.github.com/users/poeticninja/following{/other_user}","gists_url":"https://api.github.com/users/poeticninja/gists{/gist_id}","starred_url":"https://api.github.com/users/poeticninja/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/poeticninja/subscriptions","organizations_url":"https://api.github.com/users/poeticninja/orgs","repos_url":"https://api.github.com/users/poeticninja/repos","events_url":"https://api.github.com/users/poeticninja/events{/privacy}","received_events_url":"https://api.github.com/users/poeticninja/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-09-14T05:33:49Z","updated_at":"2015-09-22T23:21:11Z","closed_at":"2015-09-22T23:21:11Z","body":"First of all... the newest version of React Router is just awesome sauce. My server rendering never felt so smooth. Great job guys! :smile:\r\n\r\nI did notice that you are no longer able to access the params or the query from the context (https://github.com/rackt/react-router/blob/master/modules/RoutingContext.js#L33). I do see they are being passed down as immediate props to the routes but I am needing to access the params multiple levels deep and passing props all the way down is not very efficient. Is there another way to access the route params further down?"}}