Route parameters in React - Cheat Sheet & Quick Revision

Recall & Review

beginner

What are route parameters in React Router?

Route parameters are dynamic parts of a URL that allow you to capture values from the URL and use them inside your React components.

beginner

How do you define a route parameter in a React Router path?

You define a route parameter by adding a colon (:) before a name in the path, like /user/:id. The :id is the parameter.

beginner

How do you access route parameters inside a React component?

You use the useParams() hook from React Router. It returns an object with all route parameters as keys and their values from the URL.

beginner

Why are route parameters useful in web apps?

They let you create pages that change based on the URL, like showing details for different users or products without making separate routes for each.

beginner

Example: What will useParams() return if the URL is /product/42 and the route is /product/:productId?

It will return { productId: '42' }, so you can use productId inside your component to show product details.

How do you declare a route parameter in React Router?

A By wrapping the parameter name in curly braces, like /user/{id}

B By prefixing the parameter name with a colon, like /user/:id

C By adding a question mark after the parameter, like /user/id?

D By using a dollar sign before the parameter, like /user/$id

Route parameters are declared by prefixing the name with a colon (:), for example /user/:id.

Which React Router hook lets you access route parameters inside a component?

A useNavigate()

B useRoute()

C useLocation()

D useParams()

The useParams() hook returns an object with the current route parameters.

If your route path is /post/:postId and the URL is /post/10, what is the value of postId from useParams()?

A 10

B :postId

C post

D undefined

The postId parameter captures the value 10 from the URL.

Why use route parameters instead of separate routes for each item?

A To make URLs shorter

B To avoid using React Router

C To handle many dynamic pages with one route

D To disable navigation

Route parameters let you handle many dynamic pages with a single route definition.

What type of value does useParams() return?

A An object with keys as parameter names and values as strings from the URL

B A string with all parameters combined

C An array of parameter values

D A boolean indicating if parameters exist

useParams() returns an object where keys are parameter names and values are strings from the URL.

Explain how to use route parameters in React Router to show dynamic content based on the URL.

Think about how URLs like /user/123 can show different user info.

Describe the benefits of using route parameters in a React app.

Consider how many pages you can create with one route.

Practice

1. What does the useParams() hook in React Router do?

easy

A. It sets new route paths dynamically.

B. It retrieves the dynamic parameters from the current URL.

C. It navigates to a different route programmatically.

D. It renders a list of all available routes.

Solution

1. Step 1: Understand the purpose of useParams()

   This hook is designed to extract parameters defined in the route path from the URL.

2. Step 2: Compare with other options

   Options A, C, and D describe different React Router features, not useParams().

3. Final Answer:

   It retrieves the dynamic parameters from the current URL. -> Option B

4. Quick Check:

   useParams() = get URL parameters [OK]

Hint: Remember: useParams() reads URL values, not changes routes. [OK]

Common Mistakes:

• Confusing useParams() with navigation functions like useNavigate()
• Thinking useParams() sets or changes routes
• Assuming useParams() returns all routes instead of parameters

2. Which of the following is the correct way to define a route with a parameter named postId in React Router?

easy

A. <Route path="/post/:postId" element={<Post />} />

B. <Route path="/post/*postId" element={<Post />} />

C. <Route path="/post/postId" element={<Post />} />

D. <Route path="/post/{postId}" element={<Post />} />

Solution

1. Step 1: Identify parameter syntax in route paths

   React Router uses a colon : before the parameter name to define dynamic segments.

2. Step 2: Check each option

   <Route path="/post/:postId" element={<Post />} /> correctly uses /:postId. Options A, B, and D use incorrect syntax.

3. Final Answer:

   <Route path="/post/:postId" element={<Post />} /> -> Option A

4. Quick Check:

   Parameter syntax = colon before name [OK]

Hint: Use colon before parameter name in route path. [OK]

Common Mistakes:

• Omitting the colon before parameter name
• Using curly braces or asterisk instead of colon
• Confusing parameter syntax with query strings

3. Given the route <Route path="/profile/:username" element={<Profile />} /> and the URL /profile/jane_doe, what will useParams() return inside the Profile component?

medium

A. {"username": ":jane_doe"}

B. {"profile": "jane_doe"}

C. {"username": "jane_doe"}

D. {} (empty object)

Solution

1. Step 1: Match URL segment to route parameter

   The route defines :username as a parameter. The URL /profile/jane_doe assigns "jane_doe" to this parameter.

2. Step 2: Understand useParams() output

   useParams() returns an object with keys as parameter names and values as the matched URL parts.

3. Final Answer:

   {"username": "jane_doe"} -> Option C

4. Quick Check:

   useParams() returns {paramName: value} [OK]

Hint: useParams() keys match route parameters exactly. [OK]

Common Mistakes:

• Including colon in parameter value
• Using wrong parameter name as key
• Expecting empty object when parameter exists

4. Consider this code snippet inside a React Router app:

const params = useParams();
console.log(params.id);

But the route is defined as <Route path="/product/:productId" element={<Product />} />. What is the problem?

medium

A. The parameter name used in useParams() does not match the route parameter name.

B. useParams() cannot be used inside functional components.

C. The route path should not have a colon before the parameter name.

D. The element prop must be a string, not a component.

Solution

1. Step 1: Compare parameter names in route and code

   The route defines parameter as productId, but code accesses params.id.

2. Step 2: Understand useParams() object keys

   useParams() keys exactly match route parameter names, so params.id is undefined here.

3. Final Answer:

   The parameter name used in useParams() does not match the route parameter name. -> Option A

4. Quick Check:

   Param names must match exactly [OK]

Hint: Check parameter names match exactly in route and useParams(). [OK]

Common Mistakes:

• Assuming useParams() keys are generic like 'id'
• Thinking useParams() works outside components
• Misunderstanding route parameter syntax

5. You want to create a route that shows a user's post by user ID and post ID, like /user/42/post/7. Which route path and useParams() usage correctly extract both parameters inside the component?

hard

A. <Route path="/user/:userId/post/:postId" element={<UserPost />} />Inside component: const [userId, postId] = useParams();

B. <Route path="/user/:userId/post/:postId" element={<UserPost />} />Inside component: const params = useParams(); const user = params.user; const post = params.post;

C. <Route path="/user/:userId/post/:postId" element={<UserPost />} />Inside component: const { id1, id2 } = useParams();

D. <Route path="/user/:userId/post/:postId" element={<UserPost />} />Inside component: const { userId, postId } = useParams();

Solution

1. Step 1: Define route with multiple parameters

   The route path correctly uses :userId and :postId to capture both values.

2. Step 2: Correctly extract parameters inside component

   useParams() returns an object, so destructuring with matching keys { userId, postId } is correct. Options A, B, and C misuse keys or destructuring.

3. Final Answer:

   <Route path="/user/:userId/post/:postId" element={<UserPost />} /> with const { userId, postId } = useParams(); -> Option D

4. Quick Check:

   Multiple params = multiple keys in useParams() object [OK]

Hint: Destructure useParams() with exact route parameter names. [OK]

Common Mistakes:

• Using wrong keys when destructuring useParams()
• Trying to destructure useParams() as an array
• Accessing non-existent keys from useParams()