@fgaudo/effect-tea - v0.7.2
    Preparing search index...

    Variable andThenConst

    andThen: {
        <State, Command2, Event2>(
            next: (state: State) => Step<State, Command2, Event2>,
        ): <Command1, Event1>(
            step: Step<State, Command1, Event1>,
        ) => Step<State, Command1 | Command2, Event1 | Event2>;
        <State, Command1, Event1, Command2, Event2>(
            step: Step<State, Command1, Event1>,
            next: (state: State) => Step<State, Command2, Event2>,
        ): Step<State, Command1 | Command2, Event1 | Event2>;
    } = ...

    A step followed by another, made from its state: e.g. a parent's own step, then a child's handle, andThen(leave(state), children.Home.update({ _tag: 'ProductGone', at })). The state is the second's, and the commands and the events are both steps', in order; its lists are always present. Taking a step's state by hand to make the next one would drop its commands and its events. It is dual: andThen(next) takes the step last, for a chain of steps written with pipe.

    Type Declaration

    Settings
    Member Visibility