Replies: 2 comments 4 replies
-
|
In general, it's now advise to use See https://docs.rs/axum/latest/axum/#using-request-extensions
|
Beta Was this translation helpful? Give feedback.
-
|
what is a rule of thumb on when to use state and when to use extractors? |
Beta Was this translation helpful? Give feedback.
-
|
i also have a middleware that assigns a unique request id to each request that the handlers can access as RequestId pub struct RequestId(String);
impl RequestId {
pub fn new() -> Self {
Self(Uuid::new_v4().to_string())
}
}
let app = Router::new()
.route("/", get(home))
// some other routes ...
.layer(Extension(pool))
.layer(axum::middleware::from_fn(
|mut request: Request<Body>, next: Next| async {
let request_id = RequestId::new();
request.extensions_mut().insert(request_id);
next.run(request).await
},
));
pub async fn foo(
Extension(request_id): Extension<RequestId>,
Extension(pool): Extension<SqlitePool>,
) -> Result<StatusCode, HandlerError> { ... }should that be state or extension? |
Beta Was this translation helpful? Give feedback.
-
|
state was introduced after extension. |
Beta Was this translation helpful? Give feedback.
-
|
So, use state for application-level resources like database pools. Use request extensions for request-specific data, like request IDs or authentication information derived from cookies or headers. |
Beta Was this translation helpful? Give feedback.
-
|
You can use You could also try using |
Beta Was this translation helpful? Give feedback.
-
Summary
if i fail to layer an extension, i get this message in the response body with a 500 error
i instead want to just log it and send an empty response body.
axum version
0.7.6
Beta Was this translation helpful? Give feedback.
All reactions