Added v4 docs.

Made v4 the default version in the docs.

Signed-off-by: alexmerlin <[email protected]>

Author: alexmerlin

README.md

@@ -1,6 +1,6 @@
 # dot-controller
 
-This is DotKernel's controller package that can be use like middleware inside DotKernel or Mezzio application.
+This is Dotkernel's controller package that can be use like middleware inside Dotkernel or Mezzio application.
 It provides base classes for action based controllers similar to Laminas controller component. It is more lightweight though, but supports controller plugins and event listeners
 
 ![OSS Lifecycle](https://img.shields.io/osslifecycle/dotkernel/dot-controller)
@@ -30,14 +30,14 @@ Middleware controllers act as a handler for multiple routes. Some conventions we
 - action parameter value is converted to a method name inside the controller. Underscore, dot and line characters are removed and the action name is converted to camel-case suffixed by the string `Action`. For example a route and action pair like `/user/forgot-password` will be converted to method `forgotPasswordAction`.
 - the default action value, if not present in the URI is `index`, so you should always define an `indexAction` within your controllers for displaying a default page or redirecting.
 
-In order to create your action based controllers, you must extend the abstract class `DotKernel\DotController\AbstractActionController`
+In order to create your action based controllers, you must extend the abstract class `Dot\Controller\AbstractActionController`.
 
 ### Example
 
-Creating a UserController with default action and a register action. Will handle routes `/user` and `/user/register`
+Creating a UserController with default action and a register action. Will handle routes `/user` and `/user/register`.
 
 ```php
-use DotKernel\DotController\AbstractActionController;
+use Dot\Controller\AbstractActionController;
 
 class UserController extends AbstractActionController
 {
@@ -56,7 +56,7 @@ class UserController extends AbstractActionController
 Then register this controller as a routed middleware in file `RoutesDelegator.php` just like a regular middleware.
 
 ```php
-//Example from a DotKernel RoutesDelegator
+//Example from a RoutesDelegator
 $app->route(
     '/user[/{action}]',
     UserController::class,
@@ -72,5 +72,5 @@ Use case: You have defined a controller inside some package, with default action
 - create your own controller, independent of the package's controller which adds more actions
 - Mezzio lets you define an array of middleware for a route, so you can register this controller before the package's controller
 
-Now when a request for this route comes in, your controller will run first. DotKernel controllers are designed to ignore requests that cannot be matched to one of its methods, so if no action matches, it will call the next middleware, in our case, the second controller.
+Now when a request for this route comes in, your controller will run first. Dotkernel controllers are designed to ignore requests that cannot be matched to one of its methods, so if no action matches, it will call the next middleware, in our case, the second controller.
 If this is the last controller, and action does not match here, it will go to the default 404 Not found page(handled by NotFoundDelegate)

docs/book/v4/configuration.md

@@ -0,0 +1,5 @@
+# Configuration
+
+After installation, the package can be used immediately but if you want to use all features of the package, like plugins and events you need to register the `ConfigProvider` in your project by adding the below line to your configuration aggregator (usually: `config/config.php`):
+
+    \Dot\Controller\ConfigProvider::class

docs/book/v4/events.md

@@ -0,0 +1,178 @@
+# Events
+
+DotKernel's controller package supports events and those events can be of 2 types: global events (middleware-like) or manually dispatch  events.
+
+## Getting started
+
+- Every event listener that is triggered from a controller
+needs to implement `Dot\Controller\Event\ControllerEventListenerInterface` which actually extends `Laminas\EventManager\ListenerAggregateInterface`.
+- You can add the trait `Dot\Controller\Event\ControllerEventListenerTrait` to override the method of the interface.
+- Every event listener needs to be registered under the `['dot_controller']['event_listenenrs]` key in the ConfigProvider, and every key must be the class that you want to attach the events
+
+## Usage
+
+The events in a controller can be done in 2 different ways, a global way where an event is attached automatically to all the controllers action and works in the same way the middlewares works
+or a manually dispatchable way, where you can define to which controller the events is attached, and you can trigger the event where you want.
+
+For our example we have a UserController with some methods in it
+
+```php
+use DotKernel\DotController\AbstractActionController;
+
+class UserController extends AbstractActionController
+{
+    public function indexAction()
+    {
+        //...
+    }
+    
+    public function registerAction()
+    {
+        //...
+    }
+    
+    // post method for updating the user
+    public function updateAction()
+    {
+    
+    }
+}
+```
+
+### Example 1 - Global way
+
+First we will create the event listener
+
+```php
+use Dot\Controller\Event\ControllerEvent;
+use Dot\Controller\Event\ControllerEventListenerInterface;
+use Dot\Controller\Event\ControllerEventListenerTrait;
+
+// for the logger we assume you will use your own logger and inject it
+
+class UserUpdatedListener implements ControllerEventListenerInterface
+{
+    use ControllerEventListenerTrait;
+    
+    public function onBeforeDispatch(ControllerEvent $event): void
+    {
+        $this->logger->info('on before dispatch');
+    }
+
+    public function onAfterDispatch(ControllerEvent $event): void
+    {
+        $this->logger->info('on after dispatch');
+    }
+
+}
+```
+
+We register the event listener in the configuration key
+
+```php
+'dot_controller' => [
+    'event_listeners' => [
+        AccountController::class => [
+            UserUpdatedListener::class,
+        ]
+    ]
+]
+```
+
+As you can assume, `onBeforeDispatch` is triggered right before the controller is dispatched, and `onAfterDispatch` right
+after the controller is dispatched.
+
+With this it doesn't matter what action is accessed, the event it will run before and after the action.
+
+In addition, you can make use of the `event` variable to access information about the event.
+
+For example:
+
+```php
+// UserUpdatedListener
+public function onAfterDispatch(ControllerEvent $e): void
+    {
+        $method = $e->getTarget()->getRequest()->getMethod();
+        $action = $e->getParams()['method'];
+        if ($method == 'POST' && $action == 'updateAction') {
+            $this->logger->info('this will trigger ');
+
+        }
+    }
+```
+
+So every time the `updateAction` is accessed and the method is post,
+right after the action is dispatched, we can log that the user was updated.
+
+We can use the `onBeforeDispatch` in the same way, to log right before the user is updated.
+
+### Example 2 - Manually triggered way
+
+```php
+use Dot\Controller\Event\ControllerEvent;
+use Dot\Controller\Event\ControllerEventListenerInterface;
+use Dot\Controller\Event\ControllerEventListenerTrait;
+
+// for the logger we assume you will use your own logger and inject it
+
+class UserUpdatedListener implements ControllerEventListenerInterface
+{
+    use ControllerEventListenerTrait;
+    
+     public function attach(EventManagerInterface $events, $priority = 1): void
+    {
+        $this->listeners[] = $events->attach(
+            'user.profile.update',
+            [$this, 'userProfileUpdated'],
+            $priority
+        );
+    }
+
+    public function userProfileUpdated(ControllerEvent $event): void
+    {
+        $this->logger->info('User profile updated');
+    }
+
+}
+```
+
+The `attach` method is from the `ListenerAggregateInterface` which `ControllerEventListenerTrait`
+already is overriding it so can be used in a global way with `onBeforeDispatch` and `onAfterDispatch`
+methods, but we can make our custom event and bind it to our method.
+
+In this case we create attach an event called `user.profile.update` and bind it to the `userProfileUpdated`  method.
+
+Next we need to register the event
+
+```php
+'dot_controller' => [
+    'event_listeners' => [
+        AccountController::class => [
+            'user.profile.update' => UserUpdatedListener::class
+        ]
+    ]
+]
+```
+
+Now you can manually trigger the event from the controller using build in `dispatchEvent` method.
+
+```php
+// UserController
+// post method for updating the user
+public function updateAction()
+{
+    // logic
+    $this->dispatchEvent('user.profile.update', ['user' => $user]);
+
+}
+```
+
+As you can see we attach the `user` key to the parameters, so we can actually access it.
+
+```php
+    public function userProfileUpdated(ControllerEvent $event): void
+    {
+        $user = $event->getParams()['user'];
+        $this->logger->info('User profile updated', $user->toArray());
+    }
+```

docs/book/v4/installation.md

@@ -0,0 +1,5 @@
+# Installation
+
+Install `dot-controller` by executing the following Composer command:
+
+    composer require dotkernel/dot-controller

docs/book/v4/overview.md

@@ -0,0 +1,4 @@
+# Overview
+
+`dot-controller` is DotKernel's controller package that can be use like middleware inside DotKernel or Mezzio application.
+It provides base classes for action based controllers similar to Laminas controller component. It is more lightweight though, but supports controller plugins and event listeners

docs/book/v4/plugins.md

@@ -0,0 +1,98 @@
+# Plugins
+
+DotKernel's controller support plugins, much like controllers in a Laminas Applications.
+The package comes packed with a few built in plugins, but you can extend controller functionality with your own plugins.
+
+## Usage
+
+Any controller plugins must implement `Dot\Controller\Plugin\PluginInterface`.
+You need to create a factory in addition to the plugin and register it
+under the `['dot_controller']['plugin_manager']['factories']` with the plugin name.
+
+Once registered, a plugin can be directly accessed in any controller,
+by calling a method with the plugin's name (the service name or the key at which the plugin is registered inside the manager)
+
+Controller plugins offer the advantage of globally accessible functionality
+in any controller without to manually inject dependencies.
+Plugins should be used for functions that are common to any controller.
+Do not clutter controller's code with unnecessary plugins.
+
+### Example
+
+First we create our desired plugin, for our example a string helper
+
+```php
+class StringPlugin implements PluginInterface
+{
+
+    // any method inside the plugin needs to be public if you want to access it from a controller
+    public function toUpper(string $string): string
+    {
+        return strtoupper($string);
+    }
+}
+```
+
+We create a factory for the plugin
+
+```php
+use Psr\Container\ContainerInterface;
+
+class StringPluginFactory
+{
+
+    public function __invoke(ContainerInterface $container): StringPlugin
+    {
+        return new StringPlugin();
+    }
+
+}
+```
+
+Register the factory under the `['dot_controller']['plugin_manager']['factories']` key.
+
+```php
+'dot_controller' => [
+    'plugin_manager' => [
+        'factories' => [
+            'string' => StringPluginFactory::class
+        ]
+    ]
+]
+```
+
+You don't need to register the plugin factory to a regular dependencies in a configuration
+because `AbstractPluginManager` actually extends `ServiceManager`
+
+Access it in a controller.
+
+```php
+//inside a controller 
+$this->string(); // will return the StringPlugin class, so you can call any public method from it
+$this->string()->toUpper("test") // will return TEST
+```
+
+## Build-in plugins
+
+The package comes in with 2 default plugins ``template`` and `url`. You can use
+them in the same way as our example above.
+
+- `url` - the plugin is an instance of `Mezzio\Helper\UrlHelper`
+
+```php
+    //in a controller action 
+    /** @var UrlHelper $url */
+    $url = $this->url();
+    echo $url->generate('account', ['action' => 'foo', 'hash' => 'bar'])
+```
+
+- `template` - the plugin is an instance of `Mezzio\Template\TemplateRendererInterface`
+
+```php
+    // in a controller action
+    return new HtmlResponse(
+        $this->template->render('page::home', [
+            'foo' => 'bar'
+        ])
+    );
+```

docs/book/v4/usage.md

@@ -0,0 +1,60 @@
+# Usage
+
+Middleware controllers act as a handler for multiple routes. Some conventions were made:
+
+- register controllers in the routes array just like any mezzio middleware. The requirement is that you should define an `action` route parameter(possibly optional) anywhere inside the route(e.g `/user[/{action}]`)
+- action parameter value is converted to a method name inside the controller. Underscore, dot and line characters are removed and the action name is converted to camel-case suffixed by the string `Action`. For example a route and action pair like `/user/forgot-password` will be converted to method `forgotPasswordAction`.
+- the default action value, if not present in the URI is `index`, so you should always define an `indexAction` within your controllers for displaying a default page or redirecting.
+
+In order to create your action based controllers, you must extend the abstract class `DotKernel\DotController\AbstractActionController`
+
+## Example
+
+Creating a UserController with default action and a register action. Will handle routes `/user` and `/user/register`
+
+```php
+use DotKernel\DotController\AbstractActionController;
+
+class UserController extends AbstractActionController
+{
+    public function indexAction()
+    {
+        //...
+    }
+    
+    public function registerAction()
+    {
+        //...
+    }
+}
+```
+
+Then register this controller as a routed middleware in file `RoutesDelegator.php` just like a regular middleware.
+
+```php
+//Example from a DotKernel RoutesDelegator
+$app->route(
+    '/user[/{action}]',
+    UserController::class,
+    [RequestMethodInterface::METHOD_GET, RequestMethodInterface::METHOD_POST],
+    'user'
+);
+```
+
+### Multiple controllers for the same route
+
+Use case: You have defined a controller inside some package, with default actions. You want to add actions that fall into the same controller name(or route name more exactly). You want to do this without extending the controller provided by the package. In this case you can do the following
+
+- create your own controller, independent of the package's controller which adds more actions
+- Mezzio lets you define an array of middleware for a route, so you can register this controller before the package's controller
+
+Now when a request for this route comes in, your controller will run first. DotKernel controllers are designed to ignore requests that cannot be matched to one of its methods, so if no action matches, it will call the next middleware, in our case, the second controller.
+If this is the last controller, and action does not match here, it will go to the default 404 Not found page(handled by NotFoundDelegate)
+
+## Plugins
+
+- [Plugins](plugins.md)
+
+## Events
+
+- [Events](events.md)