Runs a request whose failure the caller does not want to fail the flow or the
screen: an ordinary failure is the outcome, kept by the caller (as its own
typed summary or simply dropped). A session-fatal failure — a checkpoint,
a lost login, a suspended or disabled account — is not background work and is
re-raised, so the flow or the enter does fail and the session problem is not
swallowed.
This is the one mechanism for a best-effort request: a screen and a flow use
it rather than each writing its own catch or Effect.ignore. The error
channel is narrowed to the session-fatal subset of the request's errors: an
ordinary failure stays in the outcome, so a caller is never asked to handle
an error the call already swallowed.
A background request is a step the screen interpreter runs (the launch
burst's, a screen's): a challenge the server raises over it is answered by
the installed detour and the request runs again
(answeringScreenInterruptions), so the burst goes on from it.
Runs a request whose failure the caller does not want to fail the flow or the screen: an ordinary failure is the outcome, kept by the caller (as its own typed summary or simply dropped). A session-fatal failure — a checkpoint, a lost login, a suspended or disabled account — is not background work and is re-raised, so the flow or the enter does fail and the session problem is not swallowed.
This is the one mechanism for a best-effort request: a screen and a flow use it rather than each writing its own
catchorEffect.ignore. The error channel is narrowed to the session-fatal subset of the request's errors: an ordinary failure stays in the outcome, so a caller is never asked to handle an error the call already swallowed.A background request is a step the screen interpreter runs (the launch burst's, a screen's): a challenge the server raises over it is answered by the installed detour and the request runs again (answeringScreenInterruptions), so the burst goes on from it.