Struct ProblemJson 

pub struct ProblemJson {
    pub detail: Cow<'static, str>,
    pub status: u16,
    pub title: &'static str,
    pub type_uri: &'static str,
}

RFC 7807 Problem Details for HTTP APIs.

Contains exactly four fields per RFC 7807: type, title, status, and detail. Serialized without serde via ProblemJson::to_json_bytes.

Fields

detail: Cow<'static, str>

Human-readable explanation specific to this occurrence.

May contain user-supplied data such as path names or MIME type strings. Dynamic values are stored as Cow::Owned; static strings as Cow::Borrowed.

status: u16

HTTP status code generated by this occurrence.

title: &'static str

Short, human-readable summary of the problem type.

Matches the standard HTTP reason phrase for the status code.

type_uri: &'static str

URI reference identifying the problem type.

This server always uses "about:blank".

Implementations

impl ProblemJson

pub fn to_json_bytes(&self) -> Vec<u8>

Serialize this problem detail as a JSON-encoded byte vector.

Emits exactly four fields in document order: "type", "title", "status", "detail". String fields are JSON-escaped (RFC 8259 §7) by the underlying writer; the status is an unquoted integer.

Uses JsonEmitter backed by struson for serialization.

Panics

Does not panic for any well-formed ProblemJson instance. The internal .expect() calls would only trigger on a bug in docspec-json (the key/value sequence is statically valid JSON and the Vec<u8> writer is infallible).

Trait Implementations

impl Debug for ProblemJson

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.