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

diff --git a/src/ui/handlers/setup.rs b/src/ui/handlers/setup.rs
new file mode 100644
index 0000000..49821cf
--- /dev/null
+++ b/src/ui/handlers/setup.rs
@@ -0,0 +1,41 @@
+use axum::{
+    extract::State,
+    response::{self, IntoResponse, Redirect},
+};
+
+use crate::{
+    app::App,
+    error::Internal,
+    ui::assets::{Asset, Assets},
+};
+
+pub async fn handler(State(app): State<App>) -> Result<Asset, Error> {
+    if app
+        .setup()
+        .completed()
+        .await
+        .map_err(Internal::from)
+        .map_err(Error::Internal)?
+    {
+        Err(Error::SetupCompleted)
+    } else {
+        Assets::index().map_err(Error::Internal)
+    }
+}
+
+#[derive(Debug, thiserror::Error)]
+pub enum Error {
+    #[error("setup already completed")]
+    SetupCompleted,
+    #[error("{0}")]
+    Internal(Internal),
+}
+
+impl IntoResponse for Error {
+    fn into_response(self) -> response::Response {
+        match self {
+            Self::SetupCompleted => Redirect::to("/login").into_response(),
+            Self::Internal(error) => error.into_response(),
+        }
+    }
+}