igpapi — Instagram private API Simulator for Node.js (API reference) 4.14.0
    Preparing search index...

    Interface OtherwiseDispatch

    What answers the screen the app shows over an effect of the screen interpreter: the server put a challenge in front (the effect failed with IgCheckpointError — at the low level a challenge is a failure, never a success path), and the platform answers it with the caller's alternative branches (Android: otherwise). The neutral layer knows none of the platform's screens; it only knows when to ask.

    pass brings the challenge up and walks it, screen by screen, until it is closed; it returns once nothing the challenge put in front is left, and the interpreter then runs the failed effect again, whole — its own requests before the refused one included. refuse is asked when that effect, run again, was interrupted once more: the platform names what the app shows and stops — no loop.

    Neither ever fails into the effect's channel: what the branches cannot settle stops the run that installed the detour (Android: the call rejects with the typed error), so the effect's own type stays what it declares. The stop travels out of the effect as the defect OtherwiseDispatchStop, whichever fiber met the challenge.

    interface OtherwiseDispatch {
        pass: (interruption: IgCheckpointError) => Effect<void>;
        refuse: (interruption: IgCheckpointError) => Effect<never>;
    }
    Index

    Properties

    Properties

    pass: (interruption: IgCheckpointError) => Effect<void>
    refuse: (interruption: IgCheckpointError) => Effect<never>