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, 27 deletions

diff --git a/src/boot/routes/get.rs b/src/boot/routes/get.rs
deleted file mode 100644
index 4873b7a..0000000
--- a/src/boot/routes/get.rs
+++ /dev/null
@@ -1,27 +0,0 @@
-use axum::{
-    extract::{Json, State},
-    response::{self, IntoResponse},
-};
-
-use crate::{app::App, boot::Snapshot, error::Internal, token::extract::Identity, user::User};
-
-pub async fn handler(State(app): State<App>, identity: Identity) -> Result<Response, Internal> {
-    let snapshot = app.boot().snapshot().await?;
-    Ok(Response {
-        user: identity.user,
-        snapshot,
-    })
-}
-
-#[derive(serde::Serialize)]
-pub struct Response {
-    pub user: User,
-    #[serde(flatten)]
-    pub snapshot: Snapshot,
-}
-
-impl IntoResponse for Response {
-    fn into_response(self) -> response::Response {
-        Json(self).into_response()
-    }
-}