Enum AppError 

pub enum AppError {
    BadRequest(String),
    NotFound(String),
    Internal(LogdiveError),
}

HTTP error surface used across all handlers.

Variants

BadRequest(String)

Client sent a malformed request. Message is user-facing.

NotFound(String)

A specific resource was not present. Message is user-facing.

Reserved for future endpoints that look up by id. The current GET /query and GET /stats never emit this; returning zero matches from a query is a 200 OK with an empty body, not a 404.

Internal(LogdiveError)

Unexpected internal failure. The underlying LogdiveError is kept for operator-side logging and is never exposed to the client.

Implementations

impl AppError

pub fn bad_request<M: Display>(msg: M) -> Self

Convenience constructor for 400 responses with a Display source.

Trait Implementations

impl Debug for AppError

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl From<LogdiveError> for AppError

Map LogdiveError variants to appropriate HTTP error classes.

This is the single source of truth for classification — handlers simply use ? and rely on this impl to do the right thing. Anything that looks like “the user sent something bad” becomes BadRequest; anything else becomes Internal.

fn from(err: LogdiveError) -> Self

Converts to this type from the input type.

impl From<QueryParseError> for AppError

Explicit bridge from QueryParseError to AppError.

parse_query in core returns Result<_, QueryParseError> directly, not wrapped in LogdiveError. Rust’s ? only performs a single conversion via From, so even though LogdiveError: From<QueryParseError> is defined in core, callers using ? on parse_query(...)? from an AppError-returning function need a direct impl. We delegate to the LogdiveError path so classification stays in one place.

fn from(err: QueryParseError) -> Self

Converts to this type from the input type.

impl IntoResponse for AppError

fn into_response(self) -> Response

Create a response.