From 39360492d9568174b28ffb2756e24d219da74a26 Mon Sep 17 00:00:00 2001 From: Nerixyz Date: Thu, 13 Jul 2023 19:20:29 +0200 Subject: [PATCH] docs: move documentation about order --- actix-web/src/app.rs | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/actix-web/src/app.rs b/actix-web/src/app.rs index 353b82b19..0731f11e4 100644 --- a/actix-web/src/app.rs +++ b/actix-web/src/app.rs @@ -323,16 +323,7 @@ where /// Middleware can be applied similarly to individual `Scope`s and `Resource`s. /// See [`Scope::wrap`](crate::Scope::wrap) and [`Resource::wrap`]. /// - /// # Middleware Order - /// Notice that the keyword for registering middleware is `wrap`. As you register middleware - /// using `wrap` in the App builder, imagine wrapping layers around an inner App. The first - /// middleware layer exposed to a Request is the outermost layer (i.e., the *last* registered in - /// the builder chain). Consequently, the *first* middleware registered in the builder chain is - /// the *last* to start executing during request processing. - /// - /// Ordering is less obvious when wrapped services also have middleware applied. In this case, - /// middlewares are run in reverse order for `App` _and then_ in reverse order for the - /// wrapped service. + /// For more info on middleware take a look at the [`middleware` module][crate::middleware]. /// /// # Examples /// ```