Service scope (root, module, component) in Angular - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to provide a service at the root level.

Angular

import { Injectable } from '@angular/core';

@Injectable({
  providedIn: '[1]'
})
export class DataService {
  constructor() {}
}

Drag options to blanks, or click blank then click option'

Acomponent

Bmodule

Croot

Dany

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'module' or 'component' instead of 'root' when you want a singleton service.

Using providedIn: 'root' makes the service available application-wide as a singleton.

2fill in blank

medium

Complete the code to provide a service only in a specific Angular module.

Angular

import { NgModule } from '@angular/core';
import { CommonModule } from '@angular/common';
import { UserService } from './user.service';

@NgModule({
  imports: [CommonModule],
  providers: [[1]]
})
export class UserModule {}

Drag options to blanks, or click blank then click option'

AAppService

BDataService

CHttpClient

DUserService

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting to add the service to the providers array.

Adding the service to root instead of the module.

Adding UserService to the providers array in the module limits its scope to that module.

3fill in blank

hard

Fix the error in the component to provide a service only for that component.

Angular

import { Component } from '@angular/core';
import { LoggerService } from './logger.service';

@Component({
  selector: 'app-logger',
  templateUrl: './logger.component.html',
  providers: [[1]]
})
export class LoggerComponent {
  constructor(private logger: LoggerService) {}
}

Drag options to blanks, or click blank then click option'

ALoggerService

BDataService

CHttpClient

DUserService

Attempts:

3 left

💡 Hint

Common Mistakes

Not adding the service to the component's providers array.

Adding the wrong service to providers.

Providing LoggerService in the component's providers array scopes it only to that component and its children.

4fill in blank

hard

Fill the blank to create a service provided in a feature module only.

Angular

import { Injectable, NgModule } from '@angular/core';

@Injectable()
export class FeatureService {}

@NgModule({
  providers: [[1]]
})
export class FeatureModule {}

Drag options to blanks, or click blank then click option'

AFeatureService

Bany

Croot

Dmodule

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'module' in providedIn which is invalid.

Not adding the service to the module providers.

Using providedIn: 'module' is not valid, so the service must be provided in the module's providers array. Here, FeatureService is added to the module providers to limit its scope.

5fill in blank

hard

Fill all three blanks to create a component-scoped service with a method call.

Angular

import { Injectable } from '@angular/core';

@Injectable()
export class CounterService {
  count = 0;
  increment() {
    this.count += 1;
  }
}

import { Component } from '@angular/core';

@Component({
  selector: 'app-counter',
  template: `<button (click)="[1]()">Increment</button> <p>Count: [2]</p>`,
  providers: [[3]]
})
export class CounterComponent {
  constructor(public counter: CounterService) {}
}

Drag options to blanks, or click blank then click option'

Acounter.increment

Bcounter.count

CCounterService

Dincrement

Attempts:

3 left

💡 Hint

Common Mistakes

Using method name without the service reference.

Not providing the service in the component.

Referencing count incorrectly in the template.

The button calls counter.increment() to increase the count. The template shows counter.count. The service is provided in the component's providers array as CounterService.

Practice

1. What does setting a service's providedIn property to 'root' mean in Angular?

easy

A. The service is a singleton shared across the entire application.

B. The service is created separately for each module.

C. The service is only available inside a specific component.

D. The service is not injectable anywhere.

Solution

1. Step 1: Understand providedIn: 'root' meaning

   This setting makes Angular create one instance of the service for the whole app.

2. Step 2: Compare with other scopes

   Unlike module or component scopes, 'root' shares the same instance everywhere.

3. Final Answer:

   The service is a singleton shared across the entire application. -> Option A

4. Quick Check:

   Service scope 'root' = singleton app-wide [OK]

Hint: Root scope means one service instance for whole app [OK]

Common Mistakes:

• Thinking 'root' creates multiple instances
• Confusing 'root' with component scope
• Assuming 'root' limits service to one module

2. Which of the following is the correct syntax to provide a service only in a specific Angular module?

easy

A. Add the service to the module's providers array

B. @Injectable({ providedIn: 'module' })

C. @Injectable({ providedIn: 'root' })

D. Add the service to the component's providers array

Solution

1. Step 1: Recall how to scope service to a module

   Angular does not support providedIn: 'module'. Instead, you add the service to the module's providers array.

2. Step 2: Check other options

   @Injectable({ providedIn: 'root' }) scopes service app-wide, Add the service to the component's providers array scopes to component, @Injectable({ providedIn: 'module' }) is invalid syntax.

3. Final Answer:

   Add the service to the module's providers array -> Option A

4. Quick Check:

   Module scope = add to module providers [OK]

Hint: Module scope means add service to module providers array [OK]

Common Mistakes:

• Using 'providedIn: module' which is invalid
• Confusing component providers with module providers
• Assuming 'root' scopes service to module only

3. Given this Angular component code:

@Component({
  selector: 'app-example',
  template: `
{{counter}}
`,
  providers: [CounterService]
})
export class ExampleComponent {
  counter = 0;
  constructor(private counterService: CounterService) {
    this.counter = this.counterService.increment();
  }
}

If two instances of app-example are rendered, what will be the value of counter in each?

medium

A. Both will show 0 because service is not provided.

B. Both will show the same incremented value shared globally.

C. Both will show 1 because each has its own service instance.

D. Both will show an error because service is missing.

Solution

1. Step 1: Understand component-level service scope

   Providing CounterService in providers inside the component creates a new instance per component.

2. Step 2: Analyze two component instances

   Each component instance gets its own service instance, so each counter starts fresh and increments once to 1.

3. Final Answer:

   Both will show 1 because each has its own service instance. -> Option C

4. Quick Check:

   Component scope = separate service instances per component [OK]

Hint: Component providers create separate service instances per component [OK]

Common Mistakes:

• Assuming service is shared globally despite component providers
• Thinking service is not provided at all
• Confusing component scope with root scope

4. You have a service provided in a feature module's providers array. However, when injecting it in a lazy-loaded module, Angular throws an error that the service is not found. What is the likely cause?

medium

A. The service is provided in the root injector, causing conflicts.

B. The lazy-loaded module has its own injector and does not see the feature module's providers.

C. The service is declared but not exported from the module.

D. The service class is missing the @Injectable decorator.

Solution

1. Step 1: Understand lazy-loaded module injectors

   Lazy-loaded modules have their own injectors and do not inherit providers from eagerly loaded modules.

2. Step 2: Identify provider visibility issue

   Since the service is provided in a feature module not loaded by the lazy module, the lazy module injector can't find it.

3. Final Answer:

   The lazy-loaded module has its own injector and does not see the feature module's providers. -> Option B

4. Quick Check:

   Lazy modules have separate injectors = missing providers [OK]

Hint: Lazy modules have isolated injectors; providers must be re-declared [OK]

Common Mistakes:

• Assuming root injector shares providers with lazy modules
• Forgetting to add @Injectable decorator
• Confusing export with provider visibility

5. You want to create a logging service that keeps a separate log for each component instance but also shares some global settings. Which service scope setup is best?

hard

A. Provide the service in root and use a static variable for logs.

B. Provide the service in root and use internal state to separate logs per component.

C. Provide the service only in a feature module's providers array.

D. Provide the service in each component's providers array and inject a global settings service from root.

Solution

1. Step 1: Separate logs per component instance

   Providing the logging service in each component's providers creates a new instance per component, isolating logs.

2. Step 2: Share global settings

   Injecting a global settings service provided in root allows sharing common configuration across all logging instances.

3. Final Answer:

   Provide the service in each component's providers array and inject a global settings service from root. -> Option D

4. Quick Check:

   Component scope for logs + root scope for settings = best mix [OK]

Hint: Use component scope for instance data, root scope for shared config [OK]

Common Mistakes:

• Using root scope for logs causes shared state issues
• Providing only in module loses per-component isolation
• Using static variables breaks instance separation