As our application evolves, we may need to change the URL paths of where our pages initially found. There are two convenience methods for this:
⚠️ Problem: Changing Routes
What if we needed to change our application from using /about for our about page to /about-us . How might we deal with this?
✅ Solution #1: Redirect
Obviously the first step is to change our original route:
const router = new VueRouter({routes: [...{path: '/about-us',name: 'About',component: About}]})If we’re using named routes then we don’t need to change our router-links at all. Otherwise we would have to. Then, since there might be links around the internet to our /about page, we want to make that redirect from /about to /about-us, with the following additional route.
const router = new VueRouter({routes: [...{ path: '/about', redirect: { name: "About" }}]})Note we’re using the named route for the redirect. We could have also used redirect: "/about-us" to get the same functionality, but this is hard-coding a URL in one more place we’d have to change if the path changed.
✅ Solution #2: Alias
Instead of redirecting the old path we might just want to alias it, meaning just provide a duplicate path to the same content. We could update that path and provide an alias to the old path:
const router = new VueRouter({routes: [...{path: '/about-us',name: 'About',component: About,alias: '/about' // <-----}]})Now the user can go to /about or /about-us and they’ll get the same content.
⚠️ Problem: Complex Routes
In the application we’ve been building in our Touring Vue Router course to view an event we go to /event/123. Some developers might prefer this URL to be /events/123, the plural. Let’s assume we want to make this change, and ensure that all our old URLs redirect properly to the new URL.
✅ Solution: Redirecting Dynamic Segments
To redirect a dynamic segment, we’ll need to get access to the params when we create the new path. To do this we’ll need to send in an anonymous function into the redirect property, like so:
📜 /src/router/index.js
...
const routes = [...{path: '/events/:id', // <--- make plural 'events'name: 'EventLayout',...},{path: '/event/:id',redirect: to => {return { name: 'EventDetails', params: { id: to.params.id } }}},Notice how inside this anonymous function we could do some complex logic if needed. Turns out we can simplify what we wrote above, because the id param will get passed along automatically. Vue Router is smart like this:
{path: '/event/:id',redirect: () => {return { name: 'EventDetails' }}
},
✅ Redirect with children
It turns out that redirect has the ability to accept children. So we can do this:
{path: '/event/:id',redirect: () => {return { name: 'EventDetails' }},children: [{ path: 'register', redirect: () => ({ name: 'EventRegister' }) },{ path: 'edit', redirect: () => ({ name: 'EventEdit' }) }]},
✅ Redirect with Wildcard
Another way we could solve this is with a wildcard, like so:
{path: '/event/:afterEvent(.*)',redirect: to => {return { path: '/events/' + to.params.afterEvent }}},This is taking whatever comes after the matching word /event/ and placing it after /events/. This is less code, and covers all children routes.
