getStaticPaths should have access to the query params

[Vince-vegas]

Next.js should put a feature on getStaticPaths to have access on Params for more dynamic routes

e.g

When you have a site like netflix the ID's of their movies are large, in your getStaticPaths you should have access to the params so you can dynamically fetch the query id on routes

[lucasbasquerotto]

I think that this would be very important, and it's even expected now that fallback is possible, being possible to generate static pages dynamically based on an id/slug. I think that query params should be accepted too, and render the same static page if the query params are the same.

For example, in my site I have pages with urls like /projects and /projects?page=2, and I don't think I should change the urls of the site to something like /projects/2 to be able to use static generation, especially considering that NextJS is already able to handle dynamic ids in the path.

In this case it would be important to be able to specify which parameters I want to use (like page), because parameters like the one when you access a link with Facebook (fbid) shouldn't generate another html (because they are not relevant to the page).

Or an alternative would be to make NextJS use the page at pages/projects/[page].js when the user accesses the url /projects?page=2, in this case I would handle internally to use the page mentioned before through the url pages/projects/2, but the browser would still show /projects?page=2. Is it possible? That is, is it possible to convert the route /projects?page=[page] to pages/projects/[page] in the application?

[lucasbasquerotto]

@lhguerra This approach is for cases in which you use only the query parameters, so the page shouldn't be allowed directly with /register/foo (if it is, I don't see much benefit of also having the query parameter, so you could use only the path parameter).

If you want access with the query parameter (only), in next.config you can deny the path to /register/foo, only allowing /register (which also accept query parameters).

[lhguerra]

thank's, this deny feature is just what I need :D

[lucasbasquerotto]

@lhguerra In my setup I place all internal pages in a specific directory, and block acess to this specific directory (it can only be accessed using rewrites). This way I don't need to deny each page specifically.

[abbou2]

@lucasbasquerotto please if I have multi parameters for example a filter like this : /register?page=2&name=test but the order of those params can change

[lucasbasquerotto]

@abbou2 My approach would be only for single parameters, or if there's a way to use a catch-all for parameters, and keep in mind that NextJS does not support query parameters yet. I specified a better approach at #17269 (comment), to handle multiple parameters, but it should be implemented by the NextJS team. That said, it doesn't seem that vercel will make changes to getStaticProps now that they are focusing on using the app directory.