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

diff --git a/src/ui/handlers/invite.rs b/src/ui/handlers/invite.rs
new file mode 100644
index 0000000..0f9580a
--- /dev/null
+++ b/src/ui/handlers/invite.rs
@@ -0,0 +1,53 @@
+use axum::{
+    extract::{Path, State},
+    response::{self, IntoResponse},
+};
+
+use crate::{
+    app::App,
+    error::Internal,
+    invite,
+    ui::{
+        assets::{Asset, Assets},
+        error::NotFound,
+    },
+};
+
+pub async fn handler(
+    State(app): State<App>,
+    Path(invite): Path<invite::Id>,
+) -> Result<Asset, Error> {
+    app.invites()
+        .get(&invite)
+        .await
+        .map_err(Error::internal)?
+        .ok_or(Error::NotFound)?;
+
+    Assets::index().map_err(Error::Internal)
+}
+
+#[derive(Debug, thiserror::Error)]
+pub enum Error {
+    #[error("invite not found")]
+    NotFound,
+    #[error("{0}")]
+    Internal(Internal),
+}
+
+impl Error {
+    fn internal(err: impl Into<Internal>) -> Self {
+        Self::Internal(err.into())
+    }
+}
+
+impl IntoResponse for Error {
+    fn into_response(self) -> response::Response {
+        match self {
+            Self::NotFound => match Assets::index() {
+                Ok(asset) => NotFound(asset).into_response(),
+                Err(internal) => internal.into_response(),
+            },
+            Self::Internal(error) => error.into_response(),
+        }
+    }
+}