Handlers are _named operations_, which can be exposed via routes.

Each domain module that exposes handlers does so through a `handlers` child module, ideally as a top-level symbol that can be plugged directly into Axum's `MethodRouter`. Modules could make exceptions to this - kill the doctrinaire inside yourself, after all - but none of the API modules that actually exist need such exceptions, and consistency is useful.

The related details of request types, URL types, response types, errors, &c &c are then organized into modules under `handlers`, along with their respective tests.

1 files changed, 1 insertions, 1 deletions

diff --git a/src/boot/mod.rs b/src/boot/mod.rs
index 2b74de1..48da4f0 100644
--- a/src/boot/mod.rs
+++ b/src/boot/mod.rs
@@ -5,7 +5,7 @@ use serde::Serialize;
 use crate::{channel::Channel, event::Sequence, message::Message, user::User};
 
 pub mod app;
-pub mod routes;
+pub mod handlers;
 
 #[derive(serde::Serialize)]
 pub struct Snapshot {