Results for “Std.App.Problem.Problem”

Use module:Std.List, kind:fn, or is:exact. Put a Pudu type after ::.

• Std.App.Problem.Problem

  A problem-details body (RFC 9457).

  type · Std.App.Problem
• Std.App.Problem.detailedInt -> Str -> Std.App.Problem.Problem

  status(code) carrying detail.

  fn · Std.App.Problem
• Std.App.Problem.explain&Std.App.Problem.ProblemError -> Str

  A one-line description of a refusal.

  fn · Std.App.Problem
• Std.App.Problem.fromReport&Std.Validate.Report -> Std.App.Problem.Problem

  A 422 problem whose errors member maps each faulty field to what it

  fn · Std.App.Problem
• Std.App.Problem.parseStr -> Result[Std.App.Problem.Problem, Std.App.Problem.ProblemError]

  Reads a problem body, as a client receiving one does.

  fn · Std.App.Problem
• Std.App.Problem.respond&Std.App.Problem.Problem -> Std.Http.Response

  The problem as a response with its status and application/problem+json.

  fn · Std.App.Problem
• Std.App.Problem.statusInt -> Std.App.Problem.Problem

  A problem of type about:blank whose title is the status's reason phrase.

  fn · Std.App.Problem
• Std.App.Problem.toJson&Std.App.Problem.Problem -> Std.Json.Json

  The problem as a JSON object: standard members first, empty ones omitted,

  fn · Std.App.Problem
• Std.App.Problem.typedStr -> Int -> Str -> Std.App.Problem.Problem

  A problem with its own type URI and title.

  fn · Std.App.Problem
• Std.App.Problem.withExtension&Std.App.Problem.Problem -> Str -> Std.Json.Json -> Std.App.Problem.Problem

  The problem with one more extension member. A name used by a standard

  fn · Std.App.Problem