Struct ProblemDetailsSchema 

#[non_exhaustive]
pub struct ProblemDetailsSchema {
    pub detail: Option<String>,
    pub status: i32,
    pub title: String,
    pub type_: String,
}

Standard error response body, returned for every non-2xx response.

This follows the RFC 7807 “Problem Details” shape: a stable machine-readable type, a short title, the repeated HTTP status code, and an optional detail string with specifics of this particular occurrence.

JSON schema

{
 "description": "Standard error response body, returned for every non-2xx response.\n\nThis follows the RFC 7807 \"Problem Details\" shape: a stable machine-readable\n`type`, a short `title`, the repeated HTTP `status` code, and an optional\n`detail` string with specifics of this particular occurrence.",
 "type": "object",
 "required": [
   "status",
   "title",
   "type"
 ],
 "properties": {
   "detail": {
     "description": "Human-readable explanation specific to this occurrence of the\nproblem, if any extra detail is available.",
     "type": [
       "string",
       "null"
     ]
   },
   "status": {
     "description": "HTTP status code of the response, repeated here for convenience.",
     "type": "integer",
     "format": "int32",
     "minimum": 0.0,
     "example": 404
   },
   "title": {
     "description": "Short, human-readable summary of the problem type. Does not vary\nbetween occurrences of the same `type`.",
     "type": "string"
   },
   "type": {
     "description": "A URI reference identifying the problem type. Stable across\noccurrences of the same error, so callers can match on it.",
     "type": "string",
     "format": "uri",
     "example": "/errors/resource-not-found"
   }
 }
}

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

detail: Option<String>

Human-readable explanation specific to this occurrence of the problem, if any extra detail is available.

status: i32

HTTP status code of the response, repeated here for convenience.

title: String

Short, human-readable summary of the problem type. Does not vary between occurrences of the same type.

type_: String

A URI reference identifying the problem type. Stable across occurrences of the same error, so callers can match on it.

Implementations

impl ProblemDetailsSchema

pub fn builder() -> ProblemDetailsSchemaBuilder

Create an instance of ProblemDetailsSchema using the builder syntax

Trait Implementations

impl Clone for ProblemDetailsSchema

fn clone(&self) -> ProblemDetailsSchema

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for ProblemDetailsSchema

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

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for ProblemDetailsSchema

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Serialize for ProblemDetailsSchema

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.