Notes
All PostsArchive
Android1App Store1C++1Cluster1CSS Specificity1CSS-in-JS1Emotion1Erlang1Input Method1iOS2JavaScript2Loaders1Networking1Node.js1Observables1Prerendering1Qt1React2React Native2RxJS2String Processing1WebEngine1Webpack2Windows2
© 2026 HUANG Cheng
All Posts
Qt and React Hybrid Development
Problem and Exploration A recent project posed an interesting question: how do you render AI chat responses with a typewriter effect inside a Qt app? One…
Feb 18, 2025
Detecting App Store Updates in React Native
Sometimes you ship an exciting new feature and want to prompt users to update right away. NetEase Cloud Music — a React Native app — does exactly this.…
Nov 15, 2024
A Little Pitfall in Erlang String Handling
I stumbled upon echo.opera.com — a service that prints out HTTP request headers — and thought it would be fun to build my own. After implementing echo_rs in…
Sep 26, 2024
Recursion in RxJS
The requirement: after a user selects or photographs an image, send it to an image-recognition API. The API rejects images over a certain size and returns…
Aug 1, 2024
The Mystery Behind RxJS iif
A common pattern in business logic: branch on a precondition to decide which API to call. For order payment, if it's a new order call the create-order…
Jun 22, 2024
React Native Pitfalls and Fixes
Publishing to Android App Stores Rejected for Privacy Violations Some Chinese app stores will reject your app with a message like "SDK reads private user…
Jun 3, 2024
Listing and Switching Input Methods on Windows
Approach 1: Via Keyboard Layout Limitation Extracting the layout ID is non-trivial — the code above uses a simplified low-word extraction. For a thorough…
Apr 20, 2024
Pre-rendering React Apps with Webpack
Background For various reasons — performance, SEO, accessibility — it's desirable for React (or other virtual DOM) apps to serve a static version of the page…
May 7, 2023
Handling CSS-in-JS Style Conflicts
A component library built with was repeatedly getting its styles overridden when integrated into a project that used multiple tech stacks. As you can see in…
Apr 22, 2023
Inside Webpack Loaders and Rules
The Problem A webpack-based React project worked fine on macOS and Linux but threw an error on Windows when processing SCSS: Re-installing and confirmed they…
Sep 29, 2022
Why Doesn't Listening on the Same Port in Multiple Node.js Cluster Workers Throw EADDRINUSE?
The Node.js docs show this pattern without any explanation of why it works: Everyone knows that listening on a port twice throws: And indeed, without : So how…
Sep 26, 2022
The Mystery Behind RxJS iif

The Mystery Behind RxJS iif

June 22, 2024

A common pattern in business logic: branch on a precondition to decide which API to call. For order payment, if it's a new order call the create-order endpoint; if the order already exists call the re-pay endpoint. The natural instinct is to reach for iif:

processOrder$
  .pipe(
    switchMap((isNewOrder) =>
      iif(
        () => isNewOrder === true,
        from(fetch("/order")),
        from(fetch("/pay")),
      ),
    ),
  )
  .subscribe();

Watching the network tab reveals something surprising — both requests fire, regardless of the condition.

network_request.webp

Digging into iif

export function iif<T, F>(
  condition: () => boolean,
  trueResult: ObservableInput<T>,
  falseResult: ObservableInput<F>,
): Observable<T | F> {
  return defer(() => (condition() ? trueResult : falseResult));
}

iif is just a thin wrapper around defer. What does defer do?

export function defer<R extends ObservableInput<any>>(
  observableFactory: () => R,
): Observable<ObservedValueOf<R>> {
  return new Observable<ObservedValueOf<R>>((subscriber) => {
    from(observableFactory()).subscribe(subscriber);
  });
}

defer creates an Observable that defers subscription until the factory function is called at subscribe-time — similar to switchMap.

The bug: iif is a function. When you pass from(fetch("/order")) and from(fetch("/pay")) as arguments, JavaScript evaluates them before iif is even called. Both fetch calls fire immediately at argument-evaluation time; iif then just selects which already-fired Observable to subscribe to.

The Fix

The simplest fix: use a ternary or if/else to avoid eagerly evaluating the branch you don't need:

processOrder$.pipe(
  switchMap((isNewOrder) =>
    isNewOrder === true ?
    from(fetch('/order')) :
    from(fetch('/pay')),
  )),
).subscribe();

If you want to keep iif for its expressiveness, wrap each branch in defer so the inner Observable is only created at subscribe-time:

of(true)
  .pipe(
    switchMap((result) =>
      iif(
        () => result === true,
        defer(() => from(fetch("/pay"))),
        defer(() => from(fetch("/order"))),
      ),
    ),
  )
  .subscribe();

Both defer calls are still invoked as iif arguments — but the from(fetch(...)) inside each is not executed until the defer Observable is subscribed to. Only the winning branch ever gets subscribed, so only one request fires.

#RxJS#JavaScript