Interface: ReportGuardMessages

API / @xmachines/play-view / index / ReportGuardMessages

Defined in: packages/play-view/src/report-guard.ts:60

What a ReportGuard writes to console.error, and what it therefore contains.

Each message is optional, and each one is a DECISION of the renderer that builds the guard. The rule that both serve is one rule: a contained failure is never silent, and a handler of the host never defeats the containment.

Properties

Property	Type	Description	Defined in
handlerThrew?	string	What console.error says when the handler of the host THROWS. A guard that carries this message CONTAINS such a throw. All five renderers carry it, so a host learns one rule: a handler of the host never defeats the containment, and a host that must escalate raises the failure from a task of its own — rethrowLater(error) of @xmachines/core/utils. Omit it only where a throw must reach the caller, which no renderer of this workspace asks for today. A renderer needs the containment when a throw that leaves the report also stops the screen of the fallback: the flag of play-vue schedules a render, the fallback of play-solid is the RETURN of the callback that reports, componentDidCatch of play-react can take the complete React root down, and a throw that leaves the onerror of Svelte leaves its own calling_on_error flag raised, which makes every later reset of the host raise svelte_boundary_reset_onerror.	packages/play-view/src/report-guard.ts:84
noHandler?	string	What console.error says when the host gave no handler. Omit it where the framework writes such a failure itself: React logs an error that a boundary caught, so play-react would report the same failure two times.	packages/play-view/src/report-guard.ts:67