Route parameters with ActivatedRoute in Angular - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

How does ActivatedRoute provide route parameters?

Consider an Angular component that uses ActivatedRoute to get route parameters. Which option correctly describes how to access a parameter named id synchronously?

Angular

constructor(private route: ActivatedRoute) {}

ngOnInit() {
  // How to get 'id' parameter synchronously?
}

A const id = this.route.snapshot.paramMap.get('id');

B const id = this.route.params['id'];

C const id = this.route.paramMap.get('id');

D const id = this.route.snapshot.params.id;

💡 Hint

Use the snapshot property for synchronous access and paramMap for safer parameter retrieval.

The ActivatedRoute provides a snapshot property for synchronous access to route parameters. The paramMap is a map-like object with a get() method to retrieve parameters safely as strings or null.

Option A correctly uses this.route.snapshot.paramMap.get('id').

❓ state_output

intermediate

What is the output when subscribing to route params?

Given this Angular component code, what will be logged when the route parameter id changes from '5' to '10'?

Angular

constructor(private route: ActivatedRoute) {}

ngOnInit() {
  this.route.params.subscribe(params => {
    console.log(params['id']);
  });
}

A 5 then 10

B Only 10

C Only 5

D No output

💡 Hint

Subscribing to params emits every time the route parameters change.

The params observable emits a new value whenever the route parameters change. So the console will log '5' first, then '10' after the parameter changes.

📝 Syntax

advanced

Identify the syntax error in accessing route parameters

Which option contains a syntax error when trying to get the userId parameter from ActivatedRoute?

Angular

constructor(private route: ActivatedRoute) {}

ngOnInit() {
  const userId = ???
}

A const userId = this.route.snapshot.paramMap.get('userId');

B const userId = this.route.paramMap.get('userId');

C const userId = this.route.snapshot.paramMap.userId;

D const userId = this.route.snapshot.params['userId'];

💡 Hint

paramMap is a map with a get() method, not a plain object.

Option C tries to access userId as a property of paramMap, which is incorrect. paramMap requires the get() method to retrieve parameters.

🔧 Debug

advanced

Why does subscribing to params not update the component property?

In this Angular component, the userId property does not update when the route parameter changes. What is the likely cause?

Angular

userId: string | null = null;

constructor(private route: ActivatedRoute) {}

ngOnInit() {
  this.route.params.subscribe(params => {
    params['userId'];
  });
}

A The <code>params</code> observable does not emit on parameter changes.

B The subscription callback does not assign the parameter to <code>userId</code>.

C The <code>userId</code> property must be declared as a number, not string.

D The <code>ActivatedRoute</code> service is not injected properly.

💡 Hint

Check if the parameter value is assigned to the component property inside the subscription.

The subscription callback reads params['userId'] but does not assign it to this.userId. So the component property remains unchanged.

🧠 Conceptual

expert

Why use paramMap over params in ActivatedRoute?

Which reason best explains why Angular recommends using paramMap instead of params to access route parameters?

A <code>params</code> only works for query parameters, not route parameters.

B <code>params</code> is deprecated and no longer emits values on parameter changes.

C <code>paramMap</code> automatically converts parameters to numbers, while <code>params</code> returns strings.

D <code>paramMap</code> provides a consistent API with methods like <code>get()</code> and handles missing parameters gracefully.

💡 Hint

Think about API consistency and handling of missing parameters.

paramMap is a map-like object with methods like get() that return null if a parameter is missing, avoiding undefined errors. It provides a cleaner and safer API than the plain object params.

Practice

1. What is the primary purpose of ActivatedRoute in Angular?

easy

A. To create new routes dynamically at runtime

B. To access route parameters and query parameters inside a component

C. To navigate programmatically between routes

D. To define routes in the Angular application

Solution

1. Step 1: Understand the role of ActivatedRoute

   ActivatedRoute is used inside a component to access information about the current route, including parameters.

2. Step 2: Differentiate from other routing services

   Defining routes is done in RouterModule, navigation uses Router service, not ActivatedRoute.

3. Final Answer:

   To access route parameters and query parameters inside a component -> Option B

4. Quick Check:

   ActivatedRoute = access route info [OK]

Hint: ActivatedRoute reads URL info inside components [OK]

Common Mistakes:

• Confusing ActivatedRoute with Router for navigation
• Thinking ActivatedRoute defines routes
• Using ActivatedRoute to create routes dynamically

2. Which of the following is the correct way to subscribe to route parameters using ActivatedRoute?

easy

A. this.route.param.subscribe(params => { const id = params['id']; });

B. this.route.params.get('id').subscribe(id => { });

C. this.route.paramMap.subscribe(params => { const id = params.get('id'); });

D. this.route.getParam('id').subscribe(id => { });

Solution

1. Step 1: Identify correct ActivatedRoute property

   The correct property to get parameters as an observable is paramMap, not params or others.

2. Step 2: Use the correct method to get parameter

   From paramMap, use get('id') to retrieve the parameter value.

3. Final Answer:

   this.route.paramMap.subscribe(params => { const id = params.get('id'); }); -> Option C

4. Quick Check:

   paramMap + get() = correct subscription [OK]

Hint: Use paramMap.subscribe and get('paramName') [OK]

Common Mistakes:

• Using this.route.params.get instead of paramMap
• Trying to subscribe directly on params.get()
• Using non-existent getParam method

3. Given this code snippet inside a component:

constructor(private route: ActivatedRoute) { }

ngOnInit() {
  this.route.paramMap.subscribe(params => {
    this.userId = params.get('userId');
  });
}

If the URL is /profile/42 and the route is defined as { path: 'profile/:userId' }, what will be the value of this.userId after initialization?

medium

A. '42'

B. 42 (number)

C. null

D. undefined

Solution

1. Step 1: Understand paramMap.get returns string

   The paramMap.get() method always returns a string or null if not found.

2. Step 2: Check route and URL match

   The route profile/:userId matches URL /profile/42, so userId is '42'.

3. Final Answer:

   '42' -> Option A

4. Quick Check:

   paramMap.get returns string '42' [OK]

Hint: paramMap.get returns string, not number [OK]

Common Mistakes:

• Assuming paramMap.get returns number type
• Expecting undefined if parameter exists
• Confusing paramMap with params object

4. Consider this code inside a component:

ngOnInit() {
  this.route.paramMap.subscribe(params => {
    this.id = params.get('id');
  });
}

But the URL is /product with no id parameter. What issue will occur?

medium

A. this.id will be null, no error occurs

B. Runtime error because 'id' parameter is missing

C. Subscription will not trigger at all

D. this.id will be undefined and cause template error

Solution

1. Step 1: Understand paramMap.get behavior when param missing

   If the parameter does not exist, paramMap.get() returns null, not an error.

2. Step 2: Check subscription behavior

   The subscription still triggers with the current paramMap, so this.id becomes null.

3. Final Answer:

   this.id will be null, no error occurs -> Option A

4. Quick Check:

   Missing param returns null, no error [OK]

Hint: Missing param returns null, not error [OK]

Common Mistakes:

• Expecting runtime error if param missing
• Thinking subscription won't trigger
• Confusing undefined with null

5. You want to create a component that updates its displayed data whenever the route parameter postId changes without recreating the component. Which approach correctly handles this using ActivatedRoute?

hard

A. Read postId once in the constructor and store it

B. Reload the entire component manually on route change

C. Use snapshot.paramMap.get('postId') only in ngOnInit

D. Subscribe to paramMap in ngOnInit and update data inside the subscription callback

Solution

1. Step 1: Understand component reuse on route param change

   Angular reuses the component instance when only route parameters change, so ngOnInit runs once.

2. Step 2: Use paramMap subscription to detect param changes

   Subscribing to paramMap lets you react to parameter changes dynamically without recreating the component.

3. Step 3: Why snapshot is insufficient

   snapshot.paramMap reads parameters only once and won't update if params change while component is active.

4. Final Answer:

   Subscribe to paramMap in ngOnInit and update data inside the subscription callback -> Option D

5. Quick Check:

   Subscribe paramMap for dynamic param changes [OK]

Hint: Subscribe to paramMap to handle param changes live [OK]

Common Mistakes:

• Using snapshot only and missing param updates
• Reading param once in constructor
• Manually reloading component instead of subscribing