axum-impl-validation

What problem does it solve?

Axum handlers can accept semantically invalid JSON because Json<T> only guarantees syntactic JSON and successful deserialization, not that the values satisfy your domain rules.

Core Features & Use Cases

• Type-level request validation: Use a custom ValidatedJson<T> extractor so invalid payloads are rejected before the handler runs.
• Correct status codes and error shapes: Preserve JsonRejection for malformed JSON (400-class) while mapping validator failures to 422 Unprocessable Entity.
• Validator-driven rules: Apply validator crate checks via #[derive(Validate)] and #[validate(...)] attributes, including email, length, ranges, must-match, nested structs, and static-regex validation.

Quick Start

Use axum-impl-validation to implement ValidatedJson<T> for your request structs, ensuring validation failures return 422 with structured ValidationErrors.