combineLatest and forkJoin for combining in Angular - Step-by-Step Execution

Concept Flow - combineLatest and forkJoin for combining

Start Observables

↓

combineLatest waits for all to emit at least once

↓

combineLatest emits new combined values on any source emit

↓

forkJoin waits for all to complete

↓

forkJoin emits combined last values once

↓

Complete

combineLatest emits combined latest values whenever any source emits after all have emitted once; forkJoin waits for all sources to complete and emits combined last values once.

Execution Sample

Angular

import { of, combineLatest, forkJoin } from 'rxjs';

const obs1 = of(1, 2);
const obs2 = of('A', 'B');

combineLatest([obs1, obs2]).subscribe(console.log);
forkJoin([obs1, obs2]).subscribe(console.log);

Shows how combineLatest emits on each new value after all emit once, while forkJoin emits once after all complete.

Execution Table

Step	Observable Emitted	combineLatest Output	forkJoin Output	Notes
1	obs1 emits 1	No output (waiting for obs2)	No output (waiting for completion)	combineLatest waits for all to emit at least once
2	obs2 emits 'A'	[1, 'A']	No output (waiting for completion)	combineLatest emits combined first values
3	obs1 emits 2	[2, 'A']	No output (waiting for completion)	combineLatest emits new combined value
4	obs2 emits 'B'	[2, 'B']	No output (waiting for completion)	combineLatest emits new combined value
5	obs1 completes	No output	No output (waiting for obs2 to complete)	forkJoin waits for all to complete
6	obs2 completes	No output	[2, 'B']	forkJoin emits combined last values once
7	Complete	Complete	Complete	Both streams complete

💡 Both observables complete, forkJoin emits combined last values once, combineLatest has emitted on each new value after initial emissions.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6	Final
obs1 value	none	1	1	2	2	2	2	completed
obs2 value	none	none	'A'	'A'	'B'	'B'	'B'	completed
combineLatest output	none	none	[1, 'A']	[2, 'A']	[2, 'B']	[2, 'B']	[2, 'B']	completed
forkJoin output	none	none	none	none	none	none	[2, 'B']	completed

Key Moments - 3 Insights

Why does combineLatest not emit when only one observable emits initially?

combineLatest waits until all observables have emitted at least once before emitting combined values, as shown in step 1 where obs1 emits but no output occurs until obs2 emits in step 2.

Why does forkJoin emit only once at the end?

forkJoin waits for all observables to complete and then emits a single combined array of their last emitted values, as seen in step 6 after both obs1 and obs2 complete.

Can combineLatest emit multiple times while forkJoin emits only once?

Yes, combineLatest emits every time any source emits after all have emitted once (steps 2, 3, 4), but forkJoin emits only once after all complete (step 6).

Visual Quiz - 3 Questions

Look at the execution table, what is the combineLatest output at step 3?

A [2, 'A']

B [1, 'B']

C [2, 'B']

D No output

💡 Hint

Check the 'combineLatest Output' column at step 3 in the execution table.

At which step does forkJoin emit its combined output?

A Step 2

B Step 4

C Step 6

D Step 3

💡 Hint

Look at the 'forkJoin Output' column in the execution table to find when it first emits.

If obs2 never emits, what would combineLatest do?

A Emit combined values immediately

B Never emit any value

C Emit only obs1 values

D Emit last value on completion

💡 Hint

Refer to the key moment about combineLatest waiting for all observables to emit at least once.

Concept Snapshot

combineLatest waits for all observables to emit once, then emits combined latest values on any new emission.
forkJoin waits for all observables to complete, then emits combined last values once.
Use combineLatest for continuous updates, forkJoin for final combined results.
Both return arrays of latest values from sources.
combineLatest emits multiple times; forkJoin emits once.

Full Transcript

This visual execution shows how combineLatest and forkJoin work in Angular. combineLatest waits until all observables have emitted at least once, then emits combined latest values every time any observable emits a new value. forkJoin waits for all observables to complete, then emits a single combined array of their last emitted values. The execution table traces emissions step-by-step, showing combineLatest emitting multiple times and forkJoin emitting once at the end. Variable tracking shows the values each observable emits and the outputs produced. Key moments clarify common confusions, such as why combineLatest waits for all to emit before output and why forkJoin emits only once after completion. The quiz tests understanding of these behaviors by referencing specific steps in the execution. The snapshot summarizes the key differences and usage of combineLatest and forkJoin for combining observables in Angular.

Practice

1. What is the main difference between combineLatest and forkJoin in Angular RxJS?

easy

A. combineLatest and forkJoin behave exactly the same.

B. combineLatest waits for all sources to complete; forkJoin emits on every source emission.

C. combineLatest emits values whenever any source emits; forkJoin emits once when all sources complete.

D. combineLatest only emits once; forkJoin emits multiple times.

Solution

1. Step 1: Understand combineLatest behavior

   combineLatest emits a new combined value whenever any source observable emits after all have emitted at least once.

2. Step 2: Understand forkJoin behavior

   forkJoin waits for all source observables to complete and then emits a single combined array of their last emitted values.

3. Final Answer:

   combineLatest emits on any change; forkJoin emits once after all complete. -> Option C

4. Quick Check:

   combineLatest = live updates, forkJoin = final result [OK]

Hint: combineLatest updates live; forkJoin waits for all done [OK]

Common Mistakes:

• Thinking forkJoin emits multiple times
• Confusing combineLatest with forkJoin completion behavior
• Assuming combineLatest waits for all to complete

2. Which of the following is the correct syntax to import combineLatest and forkJoin from RxJS in Angular?

easy

A. import { combineLatest, forkJoin } from 'rxjs/operators';

B. import { combineLatest, forkJoin } from 'rxjs';

C. import { combineLatest, forkJoin } from '@angular/core';

D. import { combineLatest, forkJoin } from 'rxjs/internal';

Solution

1. Step 1: Identify correct RxJS import path

   Both combineLatest and forkJoin are exported from the main 'rxjs' package, not from Angular core or operators.

2. Step 2: Verify common incorrect imports

   @angular/core is Angular framework code, rxjs/operators contains operators like map, filter, but not these combinators.

3. Final Answer:

   import { combineLatest, forkJoin } from 'rxjs'; -> Option B

4. Quick Check:

   RxJS combinators import from 'rxjs' [OK]

Hint: Import from 'rxjs' for combineLatest and forkJoin [OK]

Common Mistakes:

• Importing from 'rxjs/operators' instead of 'rxjs'
• Importing from '@angular/core' by mistake
• Using internal RxJS paths which are not public API

3. Given the following code, what will be logged to the console?

import { of, combineLatest } from 'rxjs';

const obs1 = of(1, 2);
const obs2 = of('A', 'B');

combineLatest([obs1, obs2]).subscribe(console.log);

medium

A. [1, 'A'], [2, 'A'], [2, 'B']

B. No output because observables complete immediately

C. [1, 'A'], [1, 'B'], [2, 'B']

D. [2, 'A'], [2, 'B']

Solution

1. Step 1: Understand of observables emitting synchronously

   Both obs1 and obs2 emit their values immediately and complete. obs1 emits 1 then 2; obs2 emits 'A' then 'B'.

2. Step 2: Analyze combineLatest with synchronous emissions

   combineLatest waits for all to emit at least once, then emits combined latest values on any emission. Since subscriptions are synchronous, obs1 emits both values first (latest from obs1 is 2), then obs2 emits 'A' (triggers [2, 'A']), then 'B' (triggers [2, 'B']).

3. Final Answer:

   [2, 'A'], [2, 'B'] -> Option D

4. Quick Check:

   Synchronous combineLatest: last of first + all of second [OK]

Hint: Synchronous combineLatest with of(): last of first + all of second [OK]

Common Mistakes:

• Thinking combineLatest emits only the final values once (forkJoin behavior)
• Thinking combineLatest emits all intermediate pairs
• Assuming no output because of immediate completion

4. Identify the error in this Angular RxJS code using forkJoin:

import { forkJoin, of } from 'rxjs';

const obs1 = of(1, 2);
const obs2 = of('A', 'B');

forkJoin([obs1, obs2]).subscribe(console.log);

medium

A. No error; code works and logs [2, 'B']

B. forkJoin requires observables to emit only once; multiple emissions cause error

C. forkJoin does not accept an array of observables

D. forkJoin emits on every emission, so output is multiple arrays

Solution

1. Step 1: Check forkJoin input and behavior

   forkJoin accepts an array of observables and waits for all to complete, then emits an array of their last emitted values.

2. Step 2: Verify observables emitting multiple values

   Observables emitting multiple values are allowed; forkJoin only emits after completion with last values. Here, obs1 emits 1 then 2, obs2 emits 'A' then 'B'. forkJoin emits [2, 'B'] once.

3. Final Answer:

   No error; code works and logs [2, 'B'] -> Option A

4. Quick Check:

   forkJoin waits for last values, no error [OK]

Hint: forkJoin accepts arrays and emits last values after completion [OK]

Common Mistakes:

• Thinking forkJoin errors on multiple emissions
• Believing forkJoin emits multiple times
• Assuming forkJoin cannot take arrays

5. You have two HTTP calls in Angular returning observables: getUser() and getOrders(). You want to display user info immediately and update orders live as they change. Which combination should you use?

hard

A. Use forkJoin for getUser() and combineLatest for getOrders() to combine results.

B. Use forkJoin to wait for both HTTP calls to complete before displaying anything.

C. Use combineLatest on both observables to get live updates for user and orders.

D. Use combineLatest for getUser() and forkJoin for getOrders() to combine results.

Solution

1. Step 1: Understand HTTP observables behavior

   HTTP calls like getUser() usually emit once and complete. Orders may update live, so getOrders() is likely a stream emitting multiple times.

2. Step 2: Choose appropriate combinators

   Use forkJoin for getUser() to wait for the single response. Use combineLatest for getOrders() to get live updates. Then combine these appropriately (e.g., nest or switchMap) to show user info immediately and update orders live.

3. Final Answer:

   Use forkJoin for getUser() and combineLatest for getOrders() -> Option A

4. Quick Check:

   Single HTTP = forkJoin, live stream = combineLatest [OK]

Hint: Use forkJoin for single HTTP, combineLatest for live streams [OK]

Common Mistakes:

• Using combineLatest for single HTTP call causing unnecessary updates
• Using forkJoin for live streams causing no updates after first emit
• Mixing combinators incorrectly causing delayed or missing data