RefreshScreen
Refetches the screen this event lives in and applies the result to it directly — the screen moves to its initial (loading) state, then to success with the new content or to its failure state, unlike GetScreen, which needs a separate event to install what came back. The request targets the screen's own id, shaped by method, body, headers and timeoutMillis. Does not consume incomingData. Dispatches onSuccess (carrying the fetched ScreenModel) when the screen was fetched and applied; onNetworkFailure(status) (carrying the failure) when the request failed with an HTTP status and a child event is wired to that exact status; onFailure (carrying the Throwable, logged) for every other failure and for HTTP failures with no status-specific event declared — only one of the latter two fires per failure, and the screen is left in its failure state either way.
Parameters
Unique identifier of this event. Defaults to a random id.
Trigger that fires this event, built via EventTriggers.
Child events chained after this one, wired to its triggers (onSuccess, onNetworkFailure, onFailure).
HTTP method used for the request. Defaults to GET.
Request body. Defaults to none.
Request headers. Defaults to none.
Request timeout, in milliseconds. Defaults to none (client default).