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

diff --git a/src/ui/routes/get.rs b/src/ui/routes/get.rs
deleted file mode 100644
index 2fcb51c..0000000
--- a/src/ui/routes/get.rs
+++ /dev/null
@@ -1,30 +0,0 @@
-use axum::response::{self, IntoResponse, Redirect};
-
-use crate::{
-    error::Internal,
-    token::extract::Identity,
-    ui::assets::{Asset, Assets},
-};
-
-pub async fn handler(identity: Option<Identity>) -> Result<Asset, Error> {
-    let _ = identity.ok_or(Error::NotLoggedIn)?;
-
-    Assets::index().map_err(Error::Internal)
-}
-
-#[derive(Debug, thiserror::Error)]
-pub enum Error {
-    #[error("not logged in")]
-    NotLoggedIn,
-    #[error("{0}")]
-    Internal(Internal),
-}
-
-impl IntoResponse for Error {
-    fn into_response(self) -> response::Response {
-        match self {
-            Self::NotLoggedIn => Redirect::temporary("/login").into_response(),
-            Self::Internal(error) => error.into_response(),
-        }
-    }
-}