From c3499d20e5a8827d22eaf933f08863ad9864a70d Mon Sep 17 00:00:00 2001 From: Ed Wilde Date: Thu, 11 Feb 2021 11:33:01 +1300 Subject: [PATCH] DOC add a callout to the deprecation notice This seems more inline with other docs pages I have seen. --- .../02_Developer_Guides/02_Controllers/05_Middlewares.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/en/02_Developer_Guides/02_Controllers/05_Middlewares.md b/docs/en/02_Developer_Guides/02_Controllers/05_Middlewares.md index 632597cbb..f834e4d24 100644 --- a/docs/en/02_Developer_Guides/02_Controllers/05_Middlewares.md +++ b/docs/en/02_Developer_Guides/02_Controllers/05_Middlewares.md @@ -6,8 +6,11 @@ summary: Create objects for modifying request and response objects across contro # HTTP Middlewares HTTP Middlewares allow you to put code that will run before or after. These might be used for -authentication, logging, caching, request processing, and many other purposes. Note this interface -replaces the SilverStripe 3 interface [RequestFilter](api:SilverStripe\Control\RequestFilter), which still works but is deprecated. +authentication, logging, caching, request processing, and many other purposes. + +[notice] +Note this interface replaces the SilverStripe 3 interface [RequestFilter](api:SilverStripe\Control\RequestFilter), which still works but is deprecated. +[/notice] To create a middleware class, implement `SilverStripe\Control\Middleware\HTTPMiddleware` and define the `process(HTTPRequest $request, callable $delegate)` method. You can do anything you like in this