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
In nuxt2 we have _param routing for dynamic urls. In nuxt/bridge, for backwards compatibility, the algorithm for dynamic URLs is the same.
Unfortunately, it is very limited, especially when you need to take more than one dynamic parameter on one page.
Maybe with some version make routing like in nuxt3 using []. Changing from _ to [] is not very hard to do, but it will bring you a lot closer to nuxt3 compatibility. And when parsing urls, warn about the need to replace _ with [].
Since it is easy changing from _ to [], it may be too difficult and unjustified to implement this idea.
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.
-
In nuxt2 we have _param routing for dynamic urls. In nuxt/bridge, for backwards compatibility, the algorithm for dynamic URLs is the same.
Unfortunately, it is very limited, especially when you need to take more than one dynamic parameter on one page.
Maybe with some version make routing like in nuxt3 using []. Changing from _ to [] is not very hard to do, but it will bring you a lot closer to nuxt3 compatibility. And when parsing urls, warn about the need to replace _ with [].
Since it is easy changing from _ to [], it may be too difficult and unjustified to implement this idea.
Beta Was this translation helpful? Give feedback.
All reactions