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
We are using named dynamic routes (path can change, but name doesn't, so all occurences of path in app are changed automaticly). Now we use api to generate dynamic routes, but can't access actual router config, so we can only staticly add this routes.. but when path changed, we need to change sitemap routes too. It will be great if we can use named routes and change only path and sitemap will still work without change
What does the proposed changes look like?
there will be router config in router parameter (probably second, so callback is still usable)
-or-
there will be some this in router function where we can access router config
This feature request is available on Nuxt community (#c83)
The text was updated successfully, but these errors were encountered:
I'm not sure to understand your request, but have you take a look to the filter feature?
It's a function that allow to filter or update the routes just before sitemap generation. On the routes parameter, you can find the name or path of each route, and thus update them dynamically.
What problem does this feature solve?
We are using named dynamic routes (path can change, but name doesn't, so all occurences of path in app are changed automaticly). Now we use api to generate dynamic routes, but can't access actual router config, so we can only staticly add this routes.. but when path changed, we need to change sitemap
routes
too. It will be great if we can use named routes and change only path and sitemap will still work without changeWhat does the proposed changes look like?
there will be router config in
router
parameter (probably second, so callback is still usable)-or-
there will be some
this
in router function where we can access router configThe text was updated successfully, but these errors were encountered: