-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
getStaticPaths uses module’s path when returning params object #139
Comments
To clarify why this might matter, I had originally intended to provide the expected path params but also preserve some intermediate metadata for |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce
microsite@next
posts.tsx
{ paths: [ { params: { id: '1' } }, { params: { id: '2' } } ] }
Expected result
Two pages will be built, with their respective content:
/posts/1.html
/posts/2.html
Observed result
Both pages will be built at
posts.html
, with whichever finished last winning.Notes and workaround
path
template static typing is cool, and it’s awesome to see that TS feature used in the wild! However, it loses inference on any other returned params.The text was updated successfully, but these errors were encountered: