api/me.ahoo.wow.api.problem

Package-level declarations

Types

What a retry of a request answered with an error may do, as the error catalog declares it for the error's code and every problem carries it (retry, with Retry-After when a retry may get past it). On the wire, lower-kebab: none, same-request, new-request.

WowProblemException

class WowProblemException @JvmOverloads constructor(val code: String, val status: Int, val retry: Retry, val retryAfter: Duration?, message: String, val result: CommandResult? = null, cause: Throwable? = null) : RuntimeException

A request Wow did not carry out for a reason of its code: the code (wow.command.busy, wow.storage.unavailable, wow.query.invalid, ...), the HTTP status it is answered with (problem+json), the command's result when it had one, and what a retry may do (retry, after retryAfter), as the error catalog says of the code. The same failure is the same exception in process and over HTTP: each boundary maps its own errors to it once.