Service-to-service injection in Angular - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is service-to-service injection in Angular?

Service-to-service injection is when one Angular service asks for another service to be provided inside it. This lets services share data or functions easily.

beginner

How do you inject a service into another service in Angular?

You add the service you want to inject as a parameter in the constructor of the service that needs it. Angular then provides it automatically.

intermediate

Why use service-to-service injection instead of calling services directly?

It keeps code clean and testable. Angular manages service creation and sharing, so you don’t create multiple copies or tightly couple services.

intermediate

What happens if you inject a service that is not provided in Angular?

Angular throws an error because it cannot find or create the service instance. You must add the service to providers or use @Injectable({providedIn: 'root'}).

advanced

Can service-to-service injection cause circular dependencies? How to avoid it?

Yes, if two services inject each other directly, it causes a circular dependency error. To avoid it, refactor code to remove direct loops or use interfaces and forwardRef.

How do you inject ServiceB into ServiceA in Angular?

A Import ServiceB in ServiceA and create new instance manually

B Call ServiceB methods directly inside ServiceA without injection

C Add ServiceB as a constructor parameter in ServiceA

D Use @Injectable decorator on ServiceA only

You inject ServiceB by adding it as a constructor parameter in ServiceA. Angular then provides the instance automatically.

What decorator must a service have to be injectable in Angular?

A @Injectable

B @Component

C @NgModule

D @Directive

The @Injectable decorator marks a class as available for dependency injection.

What error occurs if a service is injected but not provided?

A No provider for Service error

B ServiceNotFoundError

C NullPointerException

D SyntaxError

Angular throws a 'No provider for Service' error if the service is not registered in providers.

What is a common problem when two services inject each other?

A Memory leak

B Compilation warning

C Slow performance

D Circular dependency error

Injecting two services into each other creates a circular dependency error.

Where can you provide a service to make it available app-wide?

A In the component's providers array

B In the service's @Injectable decorator with providedIn: 'root'

C In the main.ts file only

D In the HTML template

Using providedIn: 'root' in @Injectable makes the service available throughout the app.

Explain how service-to-service injection works in Angular and why it is useful.

Think about how services can talk to each other without creating new instances manually.

Describe how to avoid circular dependencies when injecting services into each other.

Consider how to break the loop so services don’t depend on each other directly.

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