Skip to content

Commit c4e8f07

Browse files
Update middlewares.md
1 parent e59387e commit c4e8f07

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

content/middlewares.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -194,8 +194,6 @@ consumer
194194
195195
With the example above, `LoggerMiddleware` will be bound to all routes defined inside `CatsController` **except** the three passed to the `exclude()` method.
196196

197-
<app-banner-shop></app-banner-shop>
198-
199197
#### Functional middleware
200198

201199
The `LoggerMiddleware` class we've been using is quite simple. It has no members, no additional methods, and no dependencies. Why can't we just define it in a simple function instead of a class? In fact, we can. This type of middleware is called **functional middleware**. Let's transform the logger middleware from class-based into functional middleware to illustrate the difference:

0 commit comments

Comments
 (0)