7 releases (breaking)

0.6.0 Jan 10, 2024
0.5.1 Oct 26, 2023
0.4.0 Oct 26, 2023
0.3.0 Oct 10, 2023
0.1.0 Oct 8, 2023

#1541 in Web programming

Download history 467/week @ 2024-08-02 349/week @ 2024-08-09 300/week @ 2024-08-16 438/week @ 2024-08-23 435/week @ 2024-08-30 500/week @ 2024-09-06 343/week @ 2024-09-13 513/week @ 2024-09-20 698/week @ 2024-09-27 1059/week @ 2024-10-04 1075/week @ 2024-10-11 760/week @ 2024-10-18 933/week @ 2024-10-25 617/week @ 2024-11-01 796/week @ 2024-11-08 934/week @ 2024-11-15

3,482 downloads per month

MIT/Apache

47KB
731 lines

problem_details

Maintenance

RFC 9457 / RFC 7807 problem details for HTTP APIs.

This crate provides the ProblemDetails struct which implements the RFC 9457 / RFC 7807 problem details specification.

It supports serializing and deserializing problem details using JSON, and provides integration with the axum (0.7) and poem (2.0) web frameworks.

Usage

The following example shows how to create a problem details object that produces the example JSON from the RFC.

use http::Uri;
use problem_details::ProblemDetails;

#[derive(serde::Serialize)]
struct OutOfCreditExt {
   balance: u32,
   accounts: Vec<String>,
}

let details = ProblemDetails::new()
    .with_type(Uri::from_static("https://example.com/probs/out-of-credit"))
    .with_title("You do not have enough credit.")
    .with_detail("Your current balance is 30, but that costs 50.")
    .with_instance(Uri::from_static("/account/12345/msgs/abc"))
    .with_extensions(OutOfCreditExt {
        balance: 30,
        accounts: vec![
            "/account/12345".to_string(),
            "/account/67890".to_string(),
        ],
    });

let json = serde_json::to_value(&details).unwrap();

assert_eq!(json, serde_json::json!({
  "type": "https://example.com/probs/out-of-credit",
  "title": "You do not have enough credit.",
  "detail": "Your current balance is 30, but that costs 50.",
  "instance": "/account/12345/msgs/abc",
  "balance": 30,
  "accounts": [
    "/account/12345",
    "/account/67890"
  ]
}));

Extensions

Extensions can be added to the problem details object using the with_extensions method. The extensions are passed using a struct defining the extension fields.

During serialization, the extension fields are flattened into the problem details object.

use problem_details::ProblemDetails;

#[derive(serde::Serialize, serde::Deserialize)]
struct MyExt {
    foo: String,
    bar: u32,
}

let details = ProblemDetails::new()
    .with_title("Extensions test")
    .with_extensions(MyExt {
        foo: "Hello".to_string(),
        bar: 42,
    });

let json = serde_json::to_value(&details).unwrap();

assert_eq!(json, serde_json::json!({
  "title": "Extensions test",
  "foo": "Hello",
  "bar": 42
}));

To deserialize with extensions, provide the extensions type as the generic parameter to the ProblemDetails struct.

let details: ProblemDetails<MyExt> = serde_json::from_str(json).unwrap();

If you need dynamic extensions, you can use a HashMap as extensions object.

Features

  • serde: Enables serde support for the ProblemDetails struct (enabled by default)
  • json: Enables serialization to JSON when using web framework integrations (_enabled by default, implies serde)
  • xml: Enables serialization to XML when using web framework integrations (implies serde)
  • axum: Enables integration with the axum web framework, enabling to return ProblemDetails as responses.
  • poem: Enables integration with the poem web framework, enabling to return ProblemDetails as responses and errors.

Caveats

This crate is not fully compliant with RFC 9457, because it fails to deserialize JSON values containing properties with incorrect types (required by Chapter 3.1 of the RFC).

License

Licensed under either of

at your option.

Dependencies

~0.9–12MB
~136K SLoC