GET requests in Angular - Step-by-Step Execution

Concept Flow - GET requests

Component Initialized

↓

Call GET request method

↓

HttpClient sends GET request

↓

Server processes request

↓

Server sends response data

↓

HttpClient receives data

↓

Component updates view with data

This flow shows how an Angular component makes a GET request, waits for the server response, and updates the view with the received data.

Execution Sample

Angular

import { HttpClient } from '@angular/common/http';
import { Component } from '@angular/core';

@Component({ selector: 'app-data', template: `<div>{{data}}</div>` })
export class DataComponent {
  data = '';
  constructor(private http: HttpClient) {
    this.http.get<string>('https://api.example.com/data').subscribe(res => this.data = res);
  }
}

This Angular component sends a GET request to fetch a string and displays it in the template.

Execution Table

Step	Action	HttpClient State	Component State (data)	View Update
1	Component created	Idle	'' (empty string)	Shows empty div
2	GET request sent	Request pending	'' (empty string)	Still empty
3	Server processes request	Request pending	'' (empty string)	No change
4	Response received	Response received	'Hello World!'	Div updates to show 'Hello World!'
5	Subscription callback runs	Idle	'Hello World!'	View shows updated data

💡 GET request completes and data is displayed; no more state changes.

Variable Tracker

Variable	Start	After Step 2	After Step 4	Final
data	'' (empty string)	'' (empty string)	'Hello World!'	'Hello World!'
HttpClient State	Idle	Request pending	Response received	Idle

Key Moments - 3 Insights

Why does the component's data variable stay empty until the response arrives?

Because the GET request is asynchronous, the data variable updates only when the server sends the response, as shown in execution_table step 4.

What happens if the GET request fails or takes a long time?

The HttpClient stays in 'Request pending' state until a response or error arrives; the component data remains unchanged until then.

Why do we use subscribe() with HttpClient.get()?

Because HttpClient.get() returns an Observable, subscribe() is needed to receive the data asynchronously, as shown in step 5.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of 'data' at Step 3?

A 'Hello World!'

B '' (empty string)

C undefined

D null

💡 Hint

Check the 'Component State (data)' column at Step 3 in the execution_table.

At which step does the view update to show the fetched data?

A Step 4

B Step 1

C Step 2

D Step 3

💡 Hint

Look at the 'View Update' column in the execution_table to find when the div changes.

If the GET request took longer, which HttpClient state would persist longer?

A Idle

B Response received

C Request pending

D Error

💡 Hint

Refer to the 'HttpClient State' column in variable_tracker and execution_table steps 2 and 3.

Concept Snapshot

Angular GET requests use HttpClient.get() to fetch data asynchronously.
Use subscribe() to handle the response and update component state.
The component view updates automatically when state changes.
HttpClient states: Idle -> Request pending -> Response received.
GET requests do not block UI; data arrives later.

Full Transcript

In Angular, GET requests are made using the HttpClient service. When a component initializes, it calls HttpClient.get() with the URL. This sends a request to the server asynchronously. The component subscribes to the Observable returned by get() to receive the response data. Initially, the component's data variable is empty. When the server responds, the subscription callback updates the data variable. Angular then updates the view to show the new data. The HttpClient state changes from idle to request pending while waiting, then to response received when data arrives. This process ensures the UI stays responsive while waiting for data.