Loading states and error patterns in Angular - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a loading state in Angular applications?

A loading state is a visual indicator shown to users while data or resources are being fetched or processed. It improves user experience by signaling that the app is working and not frozen.

intermediate

How can you implement a loading state using Angular signals?

You can create a signal to track loading status (e.g., isLoading). Set it to true before starting data fetch and false after completion. Use the @if directive in the template to show a spinner or message when isLoading is true.

intermediate

What is a common pattern to handle errors in Angular components?

A common pattern is to use a signal or reactive variable to store error messages. When an error occurs during data fetch or processing, update this variable. Display the error message in the UI with clear instructions or retry options.

advanced

Why should loading and error states be accessible?

Accessible loading and error states ensure all users, including those using screen readers or keyboard navigation, understand the app status. Use ARIA roles and live regions to announce changes and provide clear focus management.

intermediate

Show an example of using Angular's @if directive to toggle loading and error messages.

In the template, use:
@if (isLoading()) { <div role='status' aria-live='polite'>Loading...</div> }
and
@if (errorMessage()) { <div role='alert'>{{ errorMessage() }}</div> }
This shows loading text when loading and error message when an error occurs.

What Angular feature helps you conditionally show loading or error messages in templates?

A NgModule

B @if directive

C Component decorator

D NgClass

The @if directive is used in Angular 17+ standalone components to conditionally render parts of the template, perfect for loading and error states.

Which ARIA role is best for announcing loading status to screen readers?

A status

B alert

C button

D navigation

The 'status' role is used for non-urgent status messages like loading indicators, announced politely by screen readers.

What is a good practice when an error occurs during data fetching in Angular?

A Ignore the error and continue

B Reload the entire page automatically

C Show a clear error message with retry option

D Hide the error silently

Showing a clear error message with a retry option helps users understand and recover from errors.

How do you track loading state in Angular using signals?

A Use a service without signals

B Use a string variable

C Use a CSS class only

D Use a boolean signal like isLoading

A boolean signal like isLoading clearly tracks whether loading is in progress.

Why is it important to manage focus when showing error messages?

A To ensure keyboard users notice the error

B To hide the error from screen readers

C To confuse users

D To disable buttons

Managing focus helps keyboard and screen reader users notice and understand errors promptly.

Explain how you would implement loading and error states in an Angular standalone component using signals and the @if directive.

Think about signals for state and template directives for showing UI changes.

Describe why accessibility is important for loading and error states and how you can improve it in Angular apps.

Consider users who rely on assistive technologies.

Practice

1. What is the main purpose of showing a loading state in an Angular component?

easy

A. To automatically refresh the page after loading

B. To hide the entire component until data is loaded

C. To disable all user interactions permanently

D. To inform the user that data is being fetched and they should wait

Solution

1. Step 1: Understand loading state purpose

   Loading states are used to show users that data is being fetched and they need to wait.

2. Step 2: Analyze options

   Only "To inform the user that data is being fetched and they should wait" correctly describes this purpose. The other options describe incorrect or unrelated behaviors.

3. Final Answer:

   To inform the user that data is being fetched and they should wait -> Option D

4. Quick Check:

   Loading state = Inform user to wait [OK]

Hint: Loading states tell users to wait, not hide or disable [OK]

Common Mistakes:

• Thinking loading hides the component completely
• Assuming loading refreshes the page
• Believing loading disables all interactions permanently

2. Which Angular syntax correctly shows a loading message only when isLoading signal is true?

easy

A. <div *ngIf="isLoading()">Loading...</div>

B. <div *ngIf="isLoading">Loading...</div>

C. <div *ngIf="isLoading = true">Loading...</div>

D. <div *ngIf="isLoading == false">Loading...</div>

Solution

1. Step 1: Understand Angular signals usage

   Signals are functions, so to get their value, you call them like isLoading().

2. Step 2: Check each option

   <div *ngIf="isLoading()">Loading...</div> correctly calls isLoading(). <div *ngIf="isLoading">Loading...</div> treats it as a property, which is incorrect for signals. <div *ngIf="isLoading = true">Loading...</div> uses assignment inside *ngIf, which is invalid. <div *ngIf="isLoading == false">Loading...</div> checks for false, which is opposite of loading.

3. Final Answer:

   <div *ngIf="isLoading()">Loading...</div> -> Option A

4. Quick Check:

   Call signals with () in *ngIf [OK]

Hint: Call signals as functions with () inside *ngIf [OK]

Common Mistakes:

• Using signal name without ()
• Trying to assign inside *ngIf
• Checking wrong boolean condition

3. Given this Angular template snippet:

<div *ngIf="error()" role="alert">Error: {{ error() }}</div>
<div *ngIf="isLoading()">Loading...</div>
<div *ngIf="!isLoading() && !error()">Data loaded</div>

What will be displayed if isLoading() returns false and error() returns "Network error"?

medium

A. Loading...

B. Error: Network error

C. Data loaded

D. Nothing is displayed

Solution

1. Step 1: Evaluate conditions with given values

   isLoading() is false, error() is "Network error" (truthy).

2. Step 2: Check which *ngIf blocks show

   The first div shows if error() is truthy, so it displays "Error: Network error". The second div shows if isLoading() is true (false here), so no. The third div shows if not loading and no error, but error exists, so no.

3. Final Answer:

   Error: Network error -> Option B

4. Quick Check:

   Error present = show error message [OK]

Hint: Error message shows if error() is truthy, regardless of loading [OK]

Common Mistakes:

• Ignoring error() and showing loading
• Showing data loaded despite error
• Assuming nothing shows when error exists

4. Identify the error in this Angular component code snippet handling loading and error states:

export class DataComponent {
  isLoading = signal(false);
  error = signal(null);

  fetchData() {
    this.isLoading = true;
    fetch('/api/data')
      .then(() => this.isLoading = false)
      .catch(err => this.error = err.message);
  }
}

medium

A. fetchData does not set error to null before fetching

B. Missing async keyword on fetchData method

C. Signals are reassigned instead of updating their value

D. No return statement in fetchData

Solution

1. Step 1: Understand how to update signals

   Signals are objects with a method to update their value, not variables to reassign.

2. Step 2: Check code for signal updates

   The code does this.isLoading = true which reassigns the signal variable instead of calling this.isLoading.set(true). Same for error.

3. Final Answer:

   Signals are reassigned instead of updating their value -> Option C

4. Quick Check:

   Update signals with .set(), not reassignment [OK]

Hint: Use .set() to update signals, not direct assignment [OK]

Common Mistakes:

• Assigning signals directly instead of using .set()
• Forgetting to reset error before fetch
• Assuming async needed without await

5. You want to show a loading spinner while data loads, an error message if loading fails, and the data content otherwise. Which Angular template pattern correctly handles these states using signals isLoading(), error(), and data()?

hard

A. <div *ngIf="isLoading()">Loading spinner...</div>
<div *ngIf="error()" role="alert">Error: {{ error() }}</div>
<div *ngIf="!isLoading() && !error()">{{ data() }}</div>

B. <div *ngIf="!isLoading()">Loading spinner...</div>
<div *ngIf="error()">Error: {{ error() }}</div>
<div *ngIf="data()">{{ data() }}</div>

C. <div *ngIf="error()">Loading spinner...</div>
<div *ngIf="isLoading()">Error: {{ error() }}</div>
<div *ngIf="data()">{{ data() }}</div>

D. <div *ngIf="data()">Loading spinner...</div>
<div *ngIf="isLoading()">Error: {{ error() }}</div>
<div *ngIf="error()">{{ data() }}</div>

Solution

1. Step 1: Understand state priorities

   Loading state should show spinner first, then error if exists, then data if no loading or error.

2. Step 2: Analyze each template option

   <div *ngIf="isLoading()">Loading spinner...</div>
   <div *ngIf="error()" role="alert">Error: {{ error() }}</div>
   <div *ngIf="!isLoading() && !error()">{{ data() }}</div>

   correctly shows loading when isLoading() is true, error message if error() is truthy, and data only if not loading and no error. The other options mix conditions incorrectly or show wrong messages for states.

3. Final Answer:

   <pre><div *ngIf="isLoading()">Loading spinner...</div> <div *ngIf="error()" role="alert">Error: {{ error() }}</div> <div *ngIf="!isLoading() && !error()">{{ data() }}</div></pre> -> Option A

4. Quick Check:

   Loading > Error > Data display order [OK]

Hint: Show loading first, then error, then data with *ngIf [OK]

Common Mistakes:

• Showing data while still loading
• Displaying error message incorrectly
• Mixing up *ngIf conditions order