docs: Update middlewares and plugins as dependencies

Author: matapatos

docs/docs/advanced-user-guide/middlewares.md

@@ -2,46 +2,47 @@ Another cool feature of WP-FastEndpoints is the support for middlewares.
 
 Middlewares are pieces of code that can either run before and/or after a request is handled.
 
-At this stage, you might be already familiar with both the `schema(...)` and `returns(...)`
-middlewares. However, you can also create your own.
+At this stage, you might be already familiar with `returns(...)` which is a middleware.
+However, you can also create your own.
 
-```php
+```php hl_lines="10 18 26"
+<?php
 use Attributes\Wp\FastEndpoints\Contracts\Middleware;
 
 class MyCustomMiddleware extends Middleware
 {
     /**
-    * Create this function if you want that your middleware is
-    * triggered when it receives a request and after checking
-    * the user permissions.
-     */
-    public function onRequest(/* Type what you need */)
-    {
-        return;
+    * This function is triggered before the main handler runs
+    * but after checking the user permissions.
+    */
+    public function onRequest(#(1))) {
+        return; #(2)
     }
 
     /**
-    * Create this function when you want your middleware to be
-    * triggered before sending a response to the client 
-     */
-    public function onResponse(/* Type what you need */) {
-        return;
+    * This function is triggered after the main handler,
+    * before sending a response to the client 
+    */
+    public function onResponse(#(3)) {
+        return; #(4)
     }
 }
 
-// Attach middleware to endpoint
 $router->get('/test', function () {
     return true;
 })
 ->middleware(new MyCustomMiddleware());
 ```
 
+1. Supports all features that a regular endpoint supports
+   e.g. [injectables](/advanced-user-guide/dependency-injection/injectables),
+   [typed request data](/advanced-user-guide/dependency-injection/request-payload)
+2. Early response return is also supported. See [Responses page](/advanced-user-guide/responses)
+3. Middlewares supports all features that a regular endpoint supports
+   e.g. [injectables](/advanced-user-guide/dependency-injection/injectables),
+   [typed request data](/advanced-user-guide/dependency-injection/request-payload)
+4. Early response return is also supported. See [Responses page](/advanced-user-guide/responses)
+
 ???+ tip
     You can create both methods in a middleware: `onRequest` and `onResponse`.
     However, to save some CPU cycles only create the one you need [CPU emoji]
-
-## Responses
-
-If you need you can also take advantage of either WP_Error and WP_REST_Response to send
-a direct response to the client. See [Responses page](/advanced-user-guide/responses)
-for more info

docs/docs/advanced-user-guide/plugins-as-dependencies.md

@@ -26,6 +26,7 @@ Currently, we support both native WP endpoints and FastEndpoints 😊
 === "With FastEndpoints"
 
     ```php
+    <?php
     $router->get('/example/all-plugins', function () {
         return "Loads all active plugins";
     });
@@ -38,6 +39,7 @@ Currently, we support both native WP endpoints and FastEndpoints 😊
 === "Native WP endpoints"
 
     ```php
+    <?php
     // Loads all active plugins
     register_rest_route('native/v1', 'example/all-plugins', [
         'methods' => 'GET',
@@ -66,6 +68,7 @@ One common scenario where router dependencies might be useful is when we want to
 of loading all active plugins per endpoint.
 
 ```php
+<?php
 $router = new \Attributes\Wp\FastEndpoints\Router('my-api', 'v1');
 $router->depends(['my-plugin']); // All endpoints and sub-routers would have this dependency
 ```