From 9157de94c34264f2766a8a0077702eabc0c14bfd Mon Sep 17 00:00:00 2001 From: Emmanuel Ferdman Date: Wed, 23 Oct 2024 07:26:36 +0300 Subject: [PATCH] update logger middleware reference (#76) Signed-off-by: Emmanuel Ferdman --- readme.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/readme.md b/readme.md index 77867ff..c304420 100644 --- a/readme.md +++ b/readme.md @@ -686,7 +686,7 @@ This seems like an unnecessarily expensive thing to do, on each request, when, i # Middlewares In general, use a [custom dispatch](#custom-dispatch) function to apply custom logic, such as logging, authentication and authorization. If you have complex route-specific logic, middleware can also be leveraged. -A middleware is a struct which exposes a nested `Config` type, a public `init` function and a public `execute` method. It can optionally define a `deinit` method. See the built-in [CORS middleware](https://github.com/karlseguin/http.zig/blob/master/src/middleware/Cors.zig) or the sample [logger middleware](https://github.com/karlseguin/http.zig/blob/master/example/middleware/Logger.zig) for examples. +A middleware is a struct which exposes a nested `Config` type, a public `init` function and a public `execute` method. It can optionally define a `deinit` method. See the built-in [CORS middleware](https://github.com/karlseguin/http.zig/blob/master/src/middleware/Cors.zig) or the sample [logger middleware](https://github.com/karlseguin/http.zig/blob/master/examples/middleware/Logger.zig) for examples. A middleware instance is created using `server.middleware()` and can then be used with the router: