Service-to-service injection in Angular - Mini Project: Build & Apply

Service-to-service injection in Angular

📖 Scenario: You are building a simple Angular app where one service needs to use another service to get data. This is common when services depend on each other to share logic or data.

🎯 Goal: Create two Angular services: DataService that provides a message, and LoggerService that uses DataService to log that message. Then inject LoggerService into a component to display the logged message.

📋 What You'll Learn

Create a service called DataService with a method getMessage() that returns the string 'Hello from DataService'.

Create a service called LoggerService that injects DataService in its constructor.

Add a method logMessage() in LoggerService that returns the message from DataService.getMessage().

Create a component called AppComponent that injects LoggerService and displays the logged message in its template.

💡 Why This Matters

🌍 Real World

Service-to-service injection is common in Angular apps to keep code modular and reusable. For example, a UserService might inject an ApiService to fetch user data.

💼 Career

Understanding dependency injection and service communication is essential for Angular developers to build maintainable and testable applications.

1

Create DataService with getMessage method

Create an Angular service called DataService with a method getMessage() that returns the string 'Hello from DataService'.

Angular

// Create DataService with getMessage method
// Your code here

Hint

Use @Injectable({ providedIn: 'root' }) to make the service available app-wide.

2

Create LoggerService injecting DataService

Create an Angular service called LoggerService that injects DataService in its constructor and stores it in a private variable called dataService.

Angular

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

@Injectable({
  providedIn: 'root'
})
export class DataService {
  getMessage(): string {
    return 'Hello from DataService';
  }
}

// Create LoggerService that injects DataService
// Your code here

Hint

Inject DataService by adding it as a private parameter in the constructor.

3

Add logMessage method in LoggerService

Add a method called logMessage() inside LoggerService that returns the result of calling getMessage() on the injected dataService.

Angular

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

@Injectable({
  providedIn: 'root'
})
export class DataService {
  getMessage(): string {
    return 'Hello from DataService';
  }
}

@Injectable({
  providedIn: 'root'
})
export class LoggerService {
  constructor(private dataService: DataService) {}

  // Add logMessage method here
  // Your code here
}

Hint

Use this.dataService.getMessage() inside logMessage().

4

Inject LoggerService in AppComponent and display message

Create an Angular component called AppComponent that injects LoggerService in its constructor. Add a public property message initialized by calling logMessage() on the injected loggerService. In the component template, display the message inside a <p> tag.

Angular

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

// Create AppComponent that injects LoggerService
// Your code here

Hint

Inject LoggerService in the constructor and assign message by calling logMessage().

Practice

1. What is the main purpose of service-to-service injection in Angular?

easy

A. To allow one service to use another service's functionality easily

B. To create multiple instances of the same service

C. To directly manipulate the DOM inside a service

D. To replace components with services

Solution

1. Step 1: Understand service-to-service injection concept

   Service-to-service injection allows one service to use another service's methods or data by injecting it via the constructor.

2. Step 2: Identify the purpose

   This helps keep code clean and reusable by sharing logic between services without duplication.

3. Final Answer:

   To allow one service to use another service's functionality easily -> Option A

4. Quick Check:

   Service-to-service injection = sharing logic between services [OK]

Hint: Services inject other services to share logic easily [OK]

Common Mistakes:

• Thinking services create multiple instances by injection
• Confusing services with components for DOM manipulation
• Believing injection replaces components with services

2. Which syntax correctly injects a service named LoggerService into another service's constructor?

easy

A. constructor(LoggerService private logger) {}

B. constructor(private LoggerService logger) {}

C. constructor(private logger: LoggerService) {}

D. constructor(logger: LoggerService private) {}

Solution

1. Step 1: Recall Angular constructor injection syntax

   Angular uses TypeScript constructor parameters with access modifiers (like private) followed by the variable name and type.

2. Step 2: Match correct syntax

   The correct form is constructor(private logger: LoggerService) {}. Other options have incorrect order or missing keywords.

3. Final Answer:

   constructor(private logger: LoggerService) {} -> Option C

4. Quick Check:

   Access modifier + variable name + type = correct injection [OK]

Hint: Use 'private varName: ServiceType' in constructor [OK]

Common Mistakes:

• Placing 'private' after the variable name
• Swapping variable name and type order
• Omitting access modifier like private or public

3. Given these services, what will DataService.getData() return?

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

@Injectable({ providedIn: 'root' })
export class LoggerService {
  log() { return 'Logged'; }
}

@Injectable({ providedIn: 'root' })
export class DataService {
  constructor(private logger: LoggerService) {}
  getData() {
    return this.logger.log() + ' Data';
  }
}

medium

A. Error: logger is undefined

B. 'Data Logged'

C. 'Logged'

D. 'Logged Data'

Solution

1. Step 1: Understand service injection and method calls

   DataService injects LoggerService and calls its log() method, which returns 'Logged'.

2. Step 2: Analyze getData() return value

   getData() returns the string from logger.log() plus ' Data', so the result is 'Logged Data'.

3. Final Answer:

   'Logged Data' -> Option D

4. Quick Check:

   Injected method output + ' Data' = 'Logged Data' [OK]

Hint: Injected service method output concatenated with string [OK]

Common Mistakes:

• Assuming logger is undefined due to missing initialization
• Mixing order of concatenated strings
• Forgetting to call the log() method

4. What is wrong with this service-to-service injection code?

@Injectable({ providedIn: 'root' })
export class UserService {
  constructor(private authService: AuthService) {}
}

// AuthService is not decorated with @Injectable

medium

A. UserService must be provided in a module, not root

B. AuthService must be decorated with @Injectable to be injected

C. Constructor should not have access modifier

D. UserService should not inject any service

Solution

1. Step 1: Check injection requirements

   Angular requires any service to be decorated with @Injectable to be injectable into other services or components.

2. Step 2: Identify missing decorator

   AuthService lacks @Injectable, so Angular cannot inject it into UserService.

3. Final Answer:

   AuthService must be decorated with @Injectable to be injected -> Option B

4. Quick Check:

   @Injectable missing on injected service = error [OK]

Hint: Always add @Injectable to services used for injection [OK]

Common Mistakes:

• Thinking access modifier in constructor is wrong
• Believing services can't be provided in root
• Assuming services can't inject other services

5. You have two services: ApiService and CacheService. You want ApiService to use CacheService to store data before returning it. Which is the best way to implement this service-to-service injection pattern?

hard

A. Inject CacheService into ApiService constructor and call cache methods inside ApiService

B. Inject ApiService into CacheService and call API methods inside CacheService

C. Create a third service that duplicates both ApiService and CacheService methods

D. Use global variables to share data between ApiService and CacheService

Solution

1. Step 1: Understand service responsibilities

   ApiService handles API calls, CacheService handles data storage. ApiService should use CacheService to store data.

2. Step 2: Apply service-to-service injection

   Inject CacheService into ApiService's constructor, then call CacheService methods inside ApiService to store data before returning it.

3. Step 3: Avoid bad patterns

   Injecting ApiService into CacheService or duplicating methods breaks separation of concerns. Using global variables is bad practice.

4. Final Answer:

   Inject CacheService into ApiService constructor and call cache methods inside ApiService -> Option A

5. Quick Check:

   Inject dependent service into main service for clean logic [OK]

Hint: Inject helper service into main service, not vice versa [OK]

Common Mistakes:

• Injecting main service into helper service causing circular dependency
• Duplicating logic instead of reusing services
• Using global variables instead of injection