You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
Currently, the rejection tracing feature in axum (version 0.7.4) works well for all axum::extract::* types when using the env_filter feature. However, it seems that rejection tracing is not implemented for axum_extra::extract::Query.
Steps to Reproduce:
Setup tracing_subscriber to enable rejection tracing:
let subscriber = tracing_subscriber::fmt().with_env_filter(
tracing_subscriber::EnvFilter::from_default_env().add_directive("axum::rejection=trace".parse().unwrap()),).finish();
tracing::subscriber::set_global_default(subscriber).expect("Failed to set up tracing");
Use axum_extra::extract::Query in your handler.
Observe that rejections from axum_extra::extract::Query are not traced to the terminal.
Expected Behavior:
Rejections from axum_extra::extract::Query should be traced to the terminal when using the rejection tracing feature in axum.
Thank you for your attention to this issue.
The text was updated successfully, but these errors were encountered:
Description:
Currently, the rejection tracing feature in axum (version 0.7.4) works well for all
axum::extract::*
types when using theenv_filter
feature. However, it seems that rejection tracing is not implemented foraxum_extra::extract::Query
.Steps to Reproduce:
tracing_subscriber
to enable rejection tracing:axum_extra::extract::Query
in your handler.axum_extra::extract::Query
are not traced to the terminal.Expected Behavior:
Rejections from
axum_extra::extract::Query
should be traced to the terminal when using the rejection tracing feature in axum.Thank you for your attention to this issue.
The text was updated successfully, but these errors were encountered: