From 8d689660b7cc1111e7b01e4987adb0c6a40120bd Mon Sep 17 00:00:00 2001 From: Merlin Beutlberger Date: Mon, 10 Jul 2023 13:30:17 +0200 Subject: [PATCH] [INTERNAL] Apply suggestions from UA review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Günter Klatt <57760635+KlattG@users.noreply.github.com> --- docs/pages/extensibility/CustomServerMiddleware.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/extensibility/CustomServerMiddleware.md b/docs/pages/extensibility/CustomServerMiddleware.md index 176adcaee8..f28a7e8385 100644 --- a/docs/pages/extensibility/CustomServerMiddleware.md +++ b/docs/pages/extensibility/CustomServerMiddleware.md @@ -249,7 +249,7 @@ In this case, a `middlewareUtil` object is provided as a part of the custom midd In the latter case, any custom middleware configured in the default `ui5.yaml` of the project will be used automatically. -However, since Karma uses the [`connect`](https://github.com/senchalabs/connect) framework, as opposed to UI5 Tooling's [`express`](https://github.com/expressjs/express), custom middleware might not always work as expected. Compared to `connect`, the `express` framework provides a greater API to middleware. +However, since Karma uses the [`connect`](https://github.com/senchalabs/connect) framework, as opposed to UI5 Tooling's [`express`](https://github.com/expressjs/express), custom middleware might not always work as expected. Compared to `connect`, the `express` framework provides a more versatile API to middleware. Therefore, if you plan to use custom middleware in an integrated scenario with `karma-ui5`, you must **restrict the middleware to using the [`connect`](https://github.com/senchalabs/connect) API only** to ensure compatibility.