Service-to-service injection in Angular

Introduction

Service-to-service injection lets one service use another service easily. It helps keep code organized and reusable.

When a service needs to get data from another service.

When you want to share logic between services without repeating code.

When a service depends on another service to perform its tasks.

When you want to keep your app modular and easy to maintain.

Syntax

Angular

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

@Injectable({ providedIn: 'root' })
export class ServiceB {
  someMethod() {
    return 'result';
  }
}

@Injectable({ providedIn: 'root' })
export class ServiceA {
  constructor(private serviceB: ServiceB) {}

  useServiceB() {
    return this.serviceB.someMethod();
  }
}

Use private in the constructor to inject the other service.

Angular automatically creates and shares the service instance.

Examples

UserService uses LoggerService to log messages before returning user data.

Angular

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

@Injectable({ providedIn: 'root' })
export class LoggerService {
  log(message: string) {
    console.log('Log:', message);
  }
}

@Injectable({ providedIn: 'root' })
export class UserService {
  constructor(private logger: LoggerService) {}

  getUser() {
    this.logger.log('Getting user');
    return { name: 'Alice' };
  }
}

DataService calls ApiService to get data, showing simple service-to-service use.

Angular

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

@Injectable({ providedIn: 'root' })
export class ApiService {
  fetchData() {
    return 'Data from API';
  }
}

@Injectable({ providedIn: 'root' })
export class DataService {
  constructor(private api: ApiService) {}

  getData() {
    return this.api.fetchData();
  }
}

Sample Program

CalculatorService uses MathService to calculate the square of a number. This shows how one service calls another.

Angular

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

@Injectable({ providedIn: 'root' })
export class MathService {
  square(num: number): number {
    return num * num;
  }
}

@Injectable({ providedIn: 'root' })
export class CalculatorService {
  constructor(private mathService: MathService) {}

  calculateSquare(num: number): number {
    return this.mathService.square(num);
  }
}

// Usage example (e.g., in a component or test):
const mathService = new MathService();
const calculatorService = new CalculatorService(mathService);
console.log(calculatorService.calculateSquare(5));

Important Notes

Always add @Injectable({ providedIn: 'root' }) to make services available app-wide.

Angular creates one instance of each service by default (singleton), so injected services share state.

Be careful to avoid circular dependencies where two services inject each other.

Summary

Service-to-service injection lets services use each other easily.

It keeps code clean and reusable by sharing logic between services.

Use Angular's @Injectable and constructor injection to connect services.

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