Use a fluent style for the middleware layers.

For endpoints that are unavailable, that default behaviour no longer needs to be specified: `Required(app)` will do that for you. For endpoints that are redirects until setup is completed, `Require(app).with_fallback(…response…)` will do that.

To make this a bit harder to break by accident, the default unavailable response is now its own type.

1 files changed, 1 insertions, 4 deletions

diff --git a/src/ui/routes/mod.rs b/src/ui/routes/mod.rs
index 328eb73..dc94773 100644
--- a/src/ui/routes/mod.rs
+++ b/src/ui/routes/mod.rs
@@ -21,10 +21,7 @@ pub fn router(app: &App) -> Router<App> {
             .route("/login", get(login::get::handler))
             .route("/ch/{channel}", get(ch::channel::get::handler))
             .route("/invite/{invite}", get(invite::invite::get::handler))
-            .route_layer(crate::setup::Required::with_fallback(
-                app.clone(),
-                Redirect::to("/setup"),
-            )),
+            .route_layer(crate::setup::Required(app.clone()).with_fallback(Redirect::to("/setup"))),
     ]
     .into_iter()
     .fold(Router::default(), Router::merge)