Blog post Leaderboard MCP Deploy agents
Back to all reviewers

Structure errors for safety

tokio-rs/axum
Based on 4 comments
Rust

Create specific error types with appropriate status codes while ensuring sensitive details are logged but not exposed to clients. Follow guidelines for defining specific error types, implementing proper status codes, logging detailed errors internally, and returning sanitized error messages to clients.

Error Handling Rust

Reviewer Prompt

Create specific error types with appropriate status codes while ensuring sensitive details are logged but not exposed to clients. Follow these guidelines:

  1. Define specific error types instead of using generic ones
  2. Implement proper status codes for each error variant
  3. Log detailed errors internally
  4. Return sanitized error messages to clients

Example:

#[derive(Debug, Error)]
pub enum ApiError {
    #[error("Invalid input provided")]
    ValidationError(#[from] JsonRejection),
    #[error("Internal server error")]
    InternalError(#[source] anyhow::Error),
}

impl IntoResponse for ApiError {
    fn into_response(self) -> Response {
        let status = match &self {
            Self::ValidationError(_) => StatusCode::UNPROCESSABLE_ENTITY,
            Self::InternalError(_) => StatusCode::INTERNAL_SERVER_ERROR,
        };
        
        // Log detailed error internally
        tracing::error!("{:#}", self);
        
        // Return sanitized response to client
        let body = Json(json!({
            "error": self.to_string()  // Uses the #[error] messages
        }));
        
        (status, body).into_response()
    }
}
4
Comments Analyzed
Rust
Primary Language
Error Handling
Category

Source Discussions