From 0d3391086d190035130bc8388ba0211b0193277f Mon Sep 17 00:00:00 2001 From: Okiki Ojo Date: Sun, 22 Mar 2026 04:35:36 -0400 Subject: [PATCH] docs: enhance operator documentation for clarity on usage and transformation concepts Signed-off-by: Okiki Ojo --- helpers/operators.ts | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/helpers/operators.ts b/helpers/operators.ts index a6d5810..c05a3d9 100644 --- a/helpers/operators.ts +++ b/helpers/operators.ts @@ -6,14 +6,15 @@ * arrive?" Operators let one Observable feed another, so a button click can * become a debounced search term, a search term can become a network request, * and a network request can become parsed JSON. + * + * Operator builders turn stream transformations into reusable pipeline stages. * - * Start with the array analogy, then extend it. `Array.map()` and - * `Array.filter()` work on values you already have in memory. Observable - * operators do similar jobs for values that arrive over time. + * `Array.map()` reshapes values already in + * memory. An Observable operator reshapes values that arrive over time. * * ```text - * array values -> map/filter -> final array - * stream values -> operators -> next Observable + * array values -> map/filter/reduce -> final array + * stream values -> operator stages -> next Observable * ``` * * That time dimension changes what the operator runtime has to manage: @@ -63,7 +64,7 @@ * // 2, 4, 6 * ``` * - * @example Recovering from bad JSON without stopping the stream + * @example Choosing pass-through mode for partial recovery * ```ts * const parseJson = createOperator({ * name: 'parseJson', -- 2.51.2