From fb7a33b1b3f9a18e1e20e25fba29b7966a16a1a4 Mon Sep 17 00:00:00 2001 From: lancedouglas1 Date: Mon, 18 Dec 2017 21:41:24 -0500 Subject: [PATCH 1/2] Update links to supported middleware topics The the pre-processing link was incorrect (pointed at static), but there also doesn't seem to be an accurate 'dynamic request handling' example. I'll add one once I figure it out in loopback if someone doesn't already. --- pages/en/lb3/Defining-middleware.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/en/lb3/Defining-middleware.md b/pages/en/lb3/Defining-middleware.md index cc3da9340..83283d0e9 100644 --- a/pages/en/lb3/Defining-middleware.md +++ b/pages/en/lb3/Defining-middleware.md @@ -18,9 +18,9 @@ Using phases helps to avoid ordering issues that can occur with standard Express LoopBack supports the following types of middleware: -* **Pre-processing middleware** for custom application logic. See [example of static middleware](#static-middleware).  +* **Pre-processing middleware** for custom application logic. See [example of pre-processing middleware](#pre-processing-middleware).  * **Dynamic request handling middleware** to serve dynamically-generated responses, for example HTML pages rendered from templates and JSON responses to REST API requests. - See [example of pre-processing middleware](#pre-processing-middleware). + See [example pending]. * **Static middleware** to serve static client-side assets.  See [example of static middleware](#static-middleware). * **Error-handling middleware** to deal with request errors. See [example of error-handling middleware](#error-handling-middleware). From 7a73d2bb8ef4c140bf435a503da221c1ac665917 Mon Sep 17 00:00:00 2001 From: lancedouglas1 Date: Tue, 19 Dec 2017 16:33:49 -0500 Subject: [PATCH 2/2] Update links to supported middleware topics (#1) The the pre-processing link was incorrect (pointed at static), but there also doesn't seem to be an accurate 'dynamic request handling' example. I'll add one once I figure it out in loopback if someone doesn't already. --- pages/en/lb3/Defining-middleware.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/pages/en/lb3/Defining-middleware.md b/pages/en/lb3/Defining-middleware.md index 83283d0e9..51466eeb3 100644 --- a/pages/en/lb3/Defining-middleware.md +++ b/pages/en/lb3/Defining-middleware.md @@ -19,8 +19,7 @@ Using phases helps to avoid ordering issues that can occur with standard Express LoopBack supports the following types of middleware: * **Pre-processing middleware** for custom application logic. See [example of pre-processing middleware](#pre-processing-middleware).  -* **Dynamic request handling middleware** to serve dynamically-generated responses, for example HTML pages rendered from templates and JSON responses to REST API requests. - See [example pending]. +* **Dynamic request handling middleware** to serve dynamically-generated responses, for example HTML pages rendered from templates and JSON responses to REST API requests. See [example pending]. * **Static middleware** to serve static client-side assets.  See [example of static middleware](#static-middleware). * **Error-handling middleware** to deal with request errors. See [example of error-handling middleware](#error-handling-middleware).