pub struct Json<T>(pub T);
Expand description
JSON Extractor / Response.
When used as an extractor, it can deserialize request bodies into some type that
implements serde::de::DeserializeOwned
. The request will be rejected (and a JsonRejection
will
be returned) if:
- The request doesn’t have a
Content-Type: application/json
(or similar) header. - The body doesn’t contain syntactically valid JSON.
- The body contains syntactically valid JSON, but it couldn’t be deserialized into the target type.
- Buffering the request body fails.
⚠️ Since parsing JSON requires consuming the request body, the Json
extractor must be
last if there are multiple extractors in a handler.
See “the order of extractors”
See JsonRejection
for more details.
§Extractor example
use axum::{
extract,
routing::post,
Router,
};
use serde::Deserialize;
#[derive(Deserialize)]
struct CreateUser {
email: String,
password: String,
}
async fn create_user(extract::Json(payload): extract::Json<CreateUser>) {
// payload is a `CreateUser`
}
let app = Router::new().route("/users", post(create_user));
When used as a response, it can serialize any type that implements serde::Serialize
to
JSON
, and will automatically set Content-Type: application/json
header.
§Response example
use axum::{
extract::Path,
routing::get,
Router,
Json,
};
use serde::Serialize;
use uuid::Uuid;
#[derive(Serialize)]
struct User {
id: Uuid,
username: String,
}
async fn get_user(Path(user_id) : Path<Uuid>) -> Json<User> {
let user = find_user(user_id).await;
Json(user)
}
async fn find_user(user_id: Uuid) -> User {
// ...
}
let app = Router::new().route("/users/:id", get(get_user));
Tuple Fields§
§0: T
Implementations§
source§impl<T> Json<T>where
T: DeserializeOwned,
impl<T> Json<T>where
T: DeserializeOwned,
sourcepub fn from_bytes(bytes: &[u8]) -> Result<Self, JsonRejection>
pub fn from_bytes(bytes: &[u8]) -> Result<Self, JsonRejection>
Construct a Json<T>
from a byte slice. Most users should prefer to use the FromRequest
impl
but special cases may require first extracting a Request
into Bytes
then optionally
constructing a Json<T>
.
Trait Implementations§
source§impl<T, S> FromRequest<S> for Json<T>
impl<T, S> FromRequest<S> for Json<T>
§type Rejection = JsonRejection
type Rejection = JsonRejection
source§impl<T> IntoResponse for Json<T>where
T: Serialize,
impl<T> IntoResponse for Json<T>where
T: Serialize,
source§fn into_response(self) -> Response
fn into_response(self) -> Response
impl<T: Copy> Copy for Json<T>
Auto Trait Implementations§
impl<T> Freeze for Json<T>where
T: Freeze,
impl<T> RefUnwindSafe for Json<T>where
T: RefUnwindSafe,
impl<T> Send for Json<T>where
T: Send,
impl<T> Sync for Json<T>where
T: Sync,
impl<T> Unpin for Json<T>where
T: Unpin,
impl<T> UnwindSafe for Json<T>where
T: UnwindSafe,
Blanket Implementations§
source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
source§impl<H, T> HandlerWithoutStateExt<T> for H
impl<H, T> HandlerWithoutStateExt<T> for H
source§fn into_service(self) -> HandlerService<H, T, ()>
fn into_service(self) -> HandlerService<H, T, ()>
Service
and no state.source§fn into_make_service(self) -> IntoMakeService<HandlerService<H, T, ()>>
fn into_make_service(self) -> IntoMakeService<HandlerService<H, T, ()>>
MakeService
and no state. Read moresource§fn into_make_service_with_connect_info<C>(
self
) -> IntoMakeServiceWithConnectInfo<HandlerService<H, T, ()>, C>
fn into_make_service_with_connect_info<C>( self ) -> IntoMakeServiceWithConnectInfo<HandlerService<H, T, ()>, C>
MakeService
which stores information
about the incoming connection and has no state. Read more