Why services are needed in Angular - Quick Recap

Recall & Review

beginner

What is the main purpose of services in Angular?

Services in Angular are used to share data and logic across multiple components, helping to keep components simple and focused on the user interface.

beginner

How do services help with code reuse in Angular?

Services allow you to write code once and use it in many components, avoiding duplication and making maintenance easier.

intermediate

Why should business logic be placed in services instead of components?

Placing business logic in services keeps components clean and focused on displaying data, making the app easier to test and maintain.

intermediate

How do services improve data sharing between components?

Services act as a single source of truth, allowing multiple components to access and update shared data consistently.

beginner

What Angular feature helps inject services into components automatically?

Angular's Dependency Injection system automatically provides services to components that need them, simplifying code and improving modularity.

Why do Angular applications use services?

A To create HTML templates

B To style components

C To handle user input events only

D To share data and logic between components

Services are designed to share data and logic across components, not for styling or templates.

Where should business logic be placed in Angular apps?

A Inside services

B Inside components only

C In HTML templates

D In CSS files

Business logic belongs in services to keep components simple and focused on UI.

How does Angular provide services to components?

A By importing CSS files

B By copying service code into components

C Using Dependency Injection

D By embedding services in HTML

Angular uses Dependency Injection to supply services to components automatically.

What problem do services solve when multiple components need the same data?

A They provide a shared data source

B They duplicate data in each component

C They prevent data sharing

D They style the data

Services act as a single source of truth for shared data.

Which of these is NOT a reason to use services in Angular?

A To keep components focused on UI

B To write CSS styles

C To handle HTTP requests

D To reuse code easily

Services are not used for styling; CSS handles styles.

Explain why Angular services are important for sharing data and logic between components.

Think about how multiple friends might share a common notebook instead of writing the same notes separately.

Describe how Angular's Dependency Injection works with services.

Imagine a helpful assistant who gives you tools exactly when you need them.

Practice

1. Why do Angular apps use services instead of putting all code inside components?

easy

A. To make components load slower

B. To share data and logic across components easily

C. To avoid using TypeScript

D. To write more HTML code

Solution

1. Step 1: Understand the role of services

   Services hold shared data and logic that multiple components can use.

2. Step 2: Compare with components

   Components focus on showing the UI, not on sharing data or logic.

3. Final Answer:

   To share data and logic across components easily -> Option B

4. Quick Check:

   Services share data and logic = A [OK]

Hint: Services share logic, components show UI [OK]

Common Mistakes:

• Thinking services slow down the app
• Believing services replace HTML
• Confusing services with components

2. Which is the correct way to inject a service into an Angular component constructor?

easy

A. constructor() { this.myService = MyService; }

B. constructor(myService = new MyService()) {}

C. constructor(public myService) {}

D. constructor(private myService: MyService) {}

Solution

1. Step 1: Recall Angular dependency injection syntax

   Angular injects services by declaring them as private/public in the constructor parameters.

2. Step 2: Check each option

   constructor(private myService: MyService) {} uses correct syntax with private and type annotation. Others create instances manually or miss type.

3. Final Answer:

   constructor(private myService: MyService) {} -> Option D

4. Quick Check:

   Use private with type in constructor = D [OK]

Hint: Use private and type in constructor for services [OK]

Common Mistakes:

• Manually creating service instances
• Missing type annotation
• Assigning service without new keyword

3. Given this service and component code, what will be logged?

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

@Component({ selector: 'app-one', template: '' })
export class OneComponent {
  constructor(private counter: CounterService) {}
  ngOnInit() { this.counter.increment(); console.log(this.counter.count); }
}

@Component({ selector: 'app-two', template: '' })
export class TwoComponent {
  constructor(private counter: CounterService) {}
  ngOnInit() { this.counter.increment(); console.log(this.counter.count); }
}

medium

A. 1 and 2

B. 1 and 1

C. 0 and 0

D. 2 and 2

Solution

1. Step 1: Understand service instance sharing

   Angular provides the same service instance to both components if the service is singleton.

2. Step 2: Trace increments and logs

   OneComponent increments count to 1 and logs 1. Then TwoComponent increments to 2 and logs 2.

3. Final Answer:

   1 and 2 -> Option A

4. Quick Check:

   Shared service count increments = C [OK]

Hint: Singleton service shares state across components [OK]

Common Mistakes:

• Assuming separate service instances per component
• Ignoring increment effect order
• Thinking count resets each time

4. What is wrong with this service usage in a component?

@Injectable({ providedIn: 'root' })
export class DataService {
  data = [];
}

@Component({ selector: 'app-test', template: '' })
export class TestComponent {
  dataService: DataService;
  constructor(private dataService: DataService) {
  }
}

medium

A. Service should be injected, not created with new

B. DataService must not have data property

C. Component must not have constructor

D. Service must be provided in component, not root

Solution

1. Step 1: Identify service instantiation method

   The component creates a new service instance manually using new, bypassing Angular's injector.

2. Step 2: Understand Angular DI pattern

   Services should be injected via constructor parameters to get the singleton instance managed by Angular.

3. Final Answer:

   Service should be injected, not created with new -> Option A

4. Quick Check:

   Inject services via constructor, not new [OK]

Hint: Never use new for services, always inject [OK]

Common Mistakes:

• Creating service instances manually
• Ignoring Angular dependency injection
• Misunderstanding providedIn usage

5. You want to share user login status across multiple components and keep UI code simple. Which approach best uses Angular services?

hard

A. Use local variables in components without services

B. Store login status in each component separately

C. Create a UserService with login status and methods, inject it in components

D. Write login logic inside each component's template

Solution

1. Step 1: Identify need for shared state

   Login status must be shared and consistent across components.

2. Step 2: Choose best practice

   Using a UserService to hold login state and methods keeps components simple and shares data.

3. Final Answer:

   Create a UserService with login status and methods, inject it in components -> Option C

4. Quick Check:

   Use service to share state and logic [OK]

Hint: Use services to share app state and logic [OK]

Common Mistakes:

• Duplicating state in components
• Putting logic in templates
• Avoiding services for shared data