variable / @typed/fx/RefStruct

omit

Omit properties from the current state of a RefStruct.

Package version
2.0.0-beta.7
Category
Derived queries
Since
1.18.0

Import

import { omit } from "@typed/fx/RefStruct";

Signatures

export declare const omit: {
    <S extends object, const Keys extends ReadonlyArray<keyof S>>(keys: Keys): <E, R>(ref: RefStruct<S, E, R>) => RefSubject.Computed<Omit<S, Keys[number]>, E, R>;
    <S extends object, const Keys extends ReadonlyArray<keyof S>, E, R>(ref: RefStruct<S, E, R>, keys: Keys): RefSubject.Computed<Omit<S, Keys[number]>, E, R>;
};

Why

Projects struct state with omit for both current reads and future pushes, avoiding a second mutable cache of the derived value.

Ownership and lifetime

The omit view retains no independent state. An Effect read samples the source once; Fx observation follows later pushes and its observing Scope owns subscription cleanup.

Other public imports

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

Source