{"action":"created","issue":{"url":"https://api.github.com/repos/zeit/next.js/issues/91","repository_url":"https://api.github.com/repos/zeit/next.js","labels_url":"https://api.github.com/repos/zeit/next.js/issues/91/labels{/name}","comments_url":"https://api.github.com/repos/zeit/next.js/issues/91/comments","events_url":"https://api.github.com/repos/zeit/next.js/issues/91/events","html_url":"https://github.com/zeit/next.js/issues/91","id":185441635,"number":91,"title":"Proposition: parameters in URL","user":{"login":"CompuIves","id":587016,"avatar_url":"https://avatars.githubusercontent.com/u/587016?v=3","gravatar_id":"","url":"https://api.github.com/users/CompuIves","html_url":"https://github.com/CompuIves","followers_url":"https://api.github.com/users/CompuIves/followers","following_url":"https://api.github.com/users/CompuIves/following{/other_user}","gists_url":"https://api.github.com/users/CompuIves/gists{/gist_id}","starred_url":"https://api.github.com/users/CompuIves/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/CompuIves/subscriptions","organizations_url":"https://api.github.com/users/CompuIves/orgs","repos_url":"https://api.github.com/users/CompuIves/repos","events_url":"https://api.github.com/users/CompuIves/events{/privacy}","received_events_url":"https://api.github.com/users/CompuIves/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":11,"created_at":"2016-10-26T16:16:28Z","updated_at":"2016-10-28T00:15:27Z","closed_at":null,"body":"I think it would be great to have parameter in URL functionality (for example `/users/:id`) while still keeping the simplicity of `next` itself. \r\n\r\nMy proposition is to do this for structure:\r\n\r\n```\r\npages/\r\n  index.js\r\n  users/\r\n    _id.js\r\n```\r\n\r\n`id.js` will be seen as a parameter path and will receive `id` as prop. You could also go further and make it like this to map `/users/:id/friends/:friendid`:\r\n\r\n```\r\npages/\r\n  index.js\r\n  users/\r\n    _id/\r\n      index.js\r\n      friends/\r\n        _friendid.js\r\n```\r\n\r\nIf the id is not specified (eg. `/users/`) then we'll first check if there is an `index.js` and otherwise use `_id.js`.\r\n\r\nI created this issue to see if others are interested in this and to see what everyones thoughts/feedback is on this. I'm willing to build this if this is a wanted feature! 😄 "},"comment":{"url":"https://api.github.com/repos/zeit/next.js/issues/comments/256805071","html_url":"https://github.com/zeit/next.js/issues/91#issuecomment-256805071","issue_url":"https://api.github.com/repos/zeit/next.js/issues/91","id":256805071,"user":{"login":"nmuth","id":5299629,"avatar_url":"https://avatars.githubusercontent.com/u/5299629?v=3","gravatar_id":"","url":"https://api.github.com/users/nmuth","html_url":"https://github.com/nmuth","followers_url":"https://api.github.com/users/nmuth/followers","following_url":"https://api.github.com/users/nmuth/following{/other_user}","gists_url":"https://api.github.com/users/nmuth/gists{/gist_id}","starred_url":"https://api.github.com/users/nmuth/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nmuth/subscriptions","organizations_url":"https://api.github.com/users/nmuth/orgs","repos_url":"https://api.github.com/users/nmuth/repos","events_url":"https://api.github.com/users/nmuth/events{/privacy}","received_events_url":"https://api.github.com/users/nmuth/received_events","type":"User","site_admin":false},"created_at":"2016-10-28T00:15:27Z","updated_at":"2016-10-28T00:15:27Z","body":"@dstreet Question about your implementation. If I have a route configuration like this:\r\n\r\n```\r\nroutes: {\r\n  '/posts/:id': 'arbitrary/directories/post'\r\n}\r\n```\r\n\r\nThen navigating to `/posts/1234` should render the component in `arbitrary/directories/post.js`, correct? What should happen if I navigate to `arbitrary/directories/post` directly? 404?"}}
{"actor":{"display_login":"nmuth"}}