Search documentation

Search by topic, API name, or import path.

GitHub ↗

variable / @typed/fx

Fx.failCause

Creates an Fx that immediately terminates with the specified Cause.

Package version
2.0.0-beta.13
Category
Failure sources
Since
1.0.0
Member of
Fx

Follow one execution

Forward the supplied whole Cause without dropping its combined failure or defect reasons.

Fx timelinefailCause(combinedCause)failCause
OperatorfailCause(combinedCause)
Read this diagram

Follow each lane from left to right. Events stacked vertically share a tick; the green cursor marks the current time across every lane.

  • A value
    The text inside the pill is the emitted value.
  • Work starts
    The raised chevron starts an inner run (^ in the source).
  • The run returns
    The vertical bar ends this lane’s run.
  • A cause is delivered
    The exclamation mark belongs to this lane.
  • Work is interrupted
    The cross marks cancellation of this run.
  • Current time
    The line and diamond move together across all lanes.
  • Happening now
    A highlighted event is at the current tick.
  • Still ahead
    Muted, dashed values have not happened yet.
  • Time continues
    The lane’s arrow is not a return marker. An empty stretch can be quiet work that is still running.

Illustrated ticks start at 0. At 1×, one illustrated tick takes one second; captions specify real durations when timing matters. A cause or interruption belongs to its lane, and other work may continue. Scroll horizontally to inspect the rest of a long timeline.

Construction is inert. Each run forwards the cause once to sink.onFailure, emits no values, and acquires no resources.

Source implementation · Learn the surrounding model

Compare all Fx timelines →

Import

import { Fx } from "@typed/fx";

Access Fx.failCause through the imported Fx export. Its declaration below describes the member.

This public exposure is a re-export. Its import path is supported; declaration documentation is shared with the other public exposures below.

Signatures

export declare const failCause: <E>(cause: Cause.Cause<E>) => Fx<never, E, never>;

Why

A complete Effect Cause can carry typed failures, defects, and interruption information across an Fx boundary without flattening that structure.

Ownership and lifetime

Construction is inert. Each run forwards the cause once to sink.onFailure, emits no values, and acquires no resources.

Examples

import { Cause, Effect } from "effect"
import { failCause, observe } from "@typed/fx/Fx"

const source = failCause(Cause.fail("offline"))
const program = observe(source, () => Effect.void).pipe(
  Effect.catch((error) => Effect.succeed(error))
)

Other public imports

These import paths expose the same declaration. Each page retains its own public name and signature.

Source