You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
but it becomes chunky and hard to deal with as soon as we get nested dynamic pages like
[lang]/[category]/[item]
even getting an error like this
```Additional keys were returned from getStaticPaths in page "/[lang]/posts/[slug]". URL Parameters intended for this dynamic route must be nested under the `params` key, i.e.:
return { params: { lang: ..., slug: ... } }
Keys that need to be moved: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9
The thing is
how about creating a tutorial on best ways to deal with multi-languages + dynamic pages, or nested dynamic routes with incremental static
and to make it worth, how about making it paid?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, I've been playing with multi-language nextjs using context,
assuming we have an array of languages, i have to do this in every page
but it becomes chunky and hard to deal with as soon as we get nested dynamic pages like
even getting an error like this
```Additional keys were returned from
getStaticPaths
in page "/[lang]/posts/[slug]". URL Parameters intended for this dynamic route must be nested under the `params` key, i.e.:return { params: { lang: ..., slug: ... } }
Keys that need to be moved: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9
Beta Was this translation helpful? Give feedback.
All reactions