Why Defining routes in Vue? - Purpose & Use Cases

The Big Idea

Discover how defining routes can turn a messy website into a smooth, easy-to-navigate app!

The Scenario

Imagine building a website with many pages, and you have to manually change the URL and show the right content every time someone clicks a link.

The Problem

Manually handling URLs and page content is confusing, slow, and easy to break. You might forget to update links or show the wrong page, making users frustrated.

The Solution

Defining routes lets you map URLs to components automatically. The framework handles showing the right page when the URL changes, so you focus on building features.

Before vs After

✗ Before

if (window.location.pathname === '/home') { showHome(); } else if (window.location.pathname === '/about') { showAbout(); }

✓ After

const routes = [{ path: '/home', component: Home }, { path: '/about', component: About }]; const router = createRouter({ routes });

What It Enables

You can create smooth, multi-page apps where navigation feels natural and works perfectly without extra manual work.

Real Life Example

Think of an online store where clicking 'Products' or 'Cart' changes the URL and page instantly, without reloading the whole site.

Key Takeaways

Manual URL handling is error-prone and hard to maintain.

Defining routes connects URLs to components automatically.

This makes navigation smooth and your code cleaner.

Practice

1. What is the main purpose of defining routes in a Vue application?

easy

A. To style components with CSS

B. To connect URLs to components so different pages can be shown

C. To manage state between components

D. To handle user input events

Solution

1. Step 1: Understand the role of routes

   Routes link specific URLs to Vue components, allowing navigation between pages.

2. Step 2: Identify the correct purpose

   Connecting URLs to components matches the description of routing.

3. Final Answer:

   To connect URLs to components so different pages can be shown -> Option B

4. Quick Check:

   Routes = URL to component mapping [OK]

Hint: Routes map URLs to components for page navigation [OK]

Common Mistakes:

• Confusing routes with styling or CSS
• Thinking routes manage state or events
• Mixing routes with user input handling

2. Which of the following is the correct way to define a route for path '/home' using a component named HomeView?

easy

A. { path: '/home', component: HomeView }

B. { route: '/home', view: HomeView }

C. { url: '/home', component: HomeView }

D. { path: '/home', view: HomeView }

Solution

1. Step 1: Recall route object keys

   Routes use keys 'path' for URL and 'component' for the Vue component.

2. Step 2: Match correct syntax

   { path: '/home', component: HomeView } uses correct keys: path and component with proper values.

3. Final Answer:

   { path: '/home', component: HomeView } -> Option A

4. Quick Check:

   Route keys = path + component [OK]

Hint: Use 'path' and 'component' keys to define routes [OK]

Common Mistakes:

• Using 'route' or 'url' instead of 'path'
• Using 'view' instead of 'component'
• Mixing keys or misspelling them

3. Given this route setup:

const routes = [
  { path: '/', component: HomeView },
  { path: '/about', component: AboutView }
];
const router = createRouter({
  history: createWebHistory(),
  routes
});

What component will show when the URL is '/about'?

medium

A. AboutView

B. HomeView

C. createRouter

D. createWebHistory

Solution

1. Step 1: Check the route matching '/about'

   The route with path '/about' uses component AboutView.

2. Step 2: Understand router behavior

   When URL is '/about', Vue Router renders AboutView component.

3. Final Answer:

   AboutView -> Option A

4. Quick Check:

   URL '/about' shows AboutView [OK]

Hint: URL matches route path to show its component [OK]

Common Mistakes:

• Confusing router functions with components
• Choosing HomeView for '/about' URL
• Not linking URL to correct route

4. Identify the error in this route definition:

const routes = [
  { path: '/contact', component ContactView }
];

medium

A. Component name should be a string

B. Path should start with '#' instead of '/'

C. Missing colon ':' after 'component'

D. Routes array should be inside createRouter

Solution

1. Step 1: Check object syntax in route

   Each key-value pair must have a colon ':' separating them.

2. Step 2: Spot missing colon after 'component'

   In the route, 'component ContactView' misses ':'; it should be 'component: ContactView'.

3. Final Answer:

   Missing colon ':' after 'component' -> Option C

4. Quick Check:

   Object syntax needs ':' [OK]

Hint: Check colons between keys and values in objects [OK]

Common Mistakes:

• Forgetting colon ':' in object properties
• Using '#' instead of '/' in paths
• Putting component names as strings incorrectly

5. You want to create a Vue router with two routes: '/' showing HomeView and '/profile/:id' showing ProfileView. Which code correctly defines these routes and sets up the router?

hard

A. const routes = [
{ path: '/', component: HomeView },
{ path: '/profile/:id', component: ProfileView }
];
const router = createRouter({
history: createMemoryHistory(),
routes
});

B. const routes = [
{ path: '/', component: HomeView },
{ path: '/profile/id', component: ProfileView }
];
const router = createRouter({
history: createWebHistory(),
routes
});

C. const routes = [
{ path: '/', component: HomeView },
{ path: '/profile/:id', component: 'ProfileView' }
];
const router = createRouter({
history: createWebHistory(),
routes
});

D. const routes = [
{ path: '/', component: HomeView },
{ path: '/profile/:id', component: ProfileView }
];
const router = createRouter({
history: createWebHistory(),
routes
});

Solution

1. Step 1: Define routes with dynamic segment

   Use '/profile/:id' to capture dynamic id parameter correctly.

2. Step 2: Use correct component references and history mode

   Components must be variables (not strings). Use createWebHistory() for normal web routing.

3. Step 3: Check each option

   const routes = [ { path: '/', component: HomeView }, { path: '/profile/:id', component: ProfileView } ]; const router = createRouter({ history: createWebHistory(), routes }); matches all requirements: dynamic path, component variables, and web history.

4. Final Answer:

   Correct route array with dynamic segment and createWebHistory() -> Option D

5. Quick Check:

   Dynamic routes use ':param' and createWebHistory() [OK]

Hint: Use ':param' for dynamic routes and createWebHistory() for browser routing [OK]

Common Mistakes:

• Using literal 'id' instead of ':id' for dynamic segments
• Passing component names as strings instead of variables
• Using createMemoryHistory() instead of createWebHistory() for web apps