-
Notifications
You must be signed in to change notification settings - Fork 27k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support /subpath/:parameter route #596
Comments
I believe you mean something like https://github.com/zeit/next.js/tree/master/examples/parameterized-routing. We don't support built-in routings, but you can implement it with custom server API. |
thank you for your quick response |
I know you guys so far decided you won't support this out of the box, but this is such an obvious and "basic" feature I feel if you provide routing at all (which you do), this should be part of it and work automagically.. |
@bassbump it's not like we don't support it. We do support it. |
@bassbump there are quite a few extensions out there:
|
Does next.js have a plan to support customized route like domain/path/:id and it will go to pages/path and use id as a query parameter?
I've made some rough changes in my forked repo
cctuan@cb31cb0
which support developer customize route in next.config.js
The text was updated successfully, but these errors were encountered: