modo-rs 0.8.0

Rust web framework for small monolithic apps
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

//! Handler-time prelude.
//!
//! `use modo::prelude::*;` in a handler or middleware module brings in the
//! ambient types reached for on nearly every request:
//!
//! - [`Error`], [`Result`] — the framework error type and alias used by `?`.
//! - [`AppState`] — the shared application state handle.
//! - [`Session`], [`Role`] — session and role extractors. Included because
//!   apps that enable them tend to want them in almost every handler; omit
//!   the glob import in crates that don't use `auth`.
//! - [`Flash`] — per-request flash messages.
//! - [`ClientIp`] — resolved client IP extractor.
//! - [`Tenant`], [`TenantId`] — multi-tenant extractor and identifier.
//! - [`Validate`], [`ValidationError`], [`Validator`] — request-body
//!   validation trait, error, and fluent helper.
//!
//! Less-universal extractors and domain types (JWT claims, OAuth providers,
//! API keys, mailer, template engine, job enqueuer, storage buckets, SSE
//! broadcaster, etc.) are intentionally NOT preluded — import them
//! explicitly from their feature-gated modules where used.

pub use crate::error::{Error, Result};
pub use crate::service::AppState;

pub use crate::auth::role::Role;
pub use crate::auth::session::Session;

pub use crate::flash::Flash;
pub use crate::ip::ClientIp;
pub use crate::tenant::{Tenant, TenantId};
pub use crate::validate::{Validate, ValidationError, Validator};