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, 0 insertions, 19 deletions

diff --git a/src/invite/routes/post.rs b/src/invite/routes/post.rs
deleted file mode 100644
index f7ca76c..0000000
--- a/src/invite/routes/post.rs
+++ /dev/null
@@ -1,19 +0,0 @@
-use axum::extract::{Json, State};
-
-use crate::{
-    app::App, clock::RequestedAt, error::Internal, invite::Invite, token::extract::Identity,
-};
-
-pub async fn handler(
-    State(app): State<App>,
-    RequestedAt(issued_at): RequestedAt,
-    identity: Identity,
-    _: Json<Request>,
-) -> Result<Json<Invite>, Internal> {
-    let invite = app.invites().issue(&identity.user, &issued_at).await?;
-    Ok(Json(invite))
-}
-
-// Require `{}` as the only valid request for this endpoint.
-#[derive(Default, serde::Deserialize)]
-pub struct Request {}