format docs

Author: DavidBadura

docs/pages/subscription.md

@@ -293,7 +293,6 @@ final class DoStuffSubscriber
     }
 }
 ```
-
 ##### Custom Resolvers
 
 You can provide your own argument resolvers by implementing the `ArgumentResolver` interface.
@@ -309,7 +308,6 @@ This is especially helpful for projectors, as they can create the necessary stru
 use Doctrine\DBAL\Connection;
 use Patchlevel\EventSourcing\Attribute\Projector;
 use Patchlevel\EventSourcing\Attribute\Setup;
-use Patchlevel\EventSourcing\Attribute\Teardown;
 
 #[Projector(self::TABLE)]
 final class ProfileProjector
@@ -352,7 +350,6 @@ For this there is the attributes `Teardown`.
 ```php
 use Doctrine\DBAL\Connection;
 use Patchlevel\EventSourcing\Attribute\Projector;
-use Patchlevel\EventSourcing\Attribute\Setup;
 use Patchlevel\EventSourcing\Attribute\Teardown;
 
 #[Projector(self::TABLE)]
@@ -361,7 +358,7 @@ final class ProfileProjector
     private const TABLE = 'profile_v1';
 
     private Connection $connection;
-    
+
     #[Teardown]
     public function drop(): void
     {
@@ -374,7 +371,7 @@ final class ProfileProjector
     MySQL and MariaDB don't support transactions for DDL statements.
     So you must use a different database connection in your projectors, 
     otherwise you will get an error when the subscription tries to create the table.
-
+    
 !!! warning
 
     A teardown can only be performed for a subscription if the code for the subscriber with that subscriber ID still exists.
@@ -383,20 +380,19 @@ final class ProfileProjector
 !!! note
 
     You can not mix the `cleanup` method with the `teardown` method.
-
+    
 ### Cleanup
 
 Alternativ, you can use a `cleanup` method for cleanup tasks.
 Unlike Teardown, this method is called when the subscription is created.
 The tasks are then saved in the Subscription Store.
-When removing the subscription, the subscriber is not necessary anymore, 
+When removing the subscription, the subscriber is not necessary anymore,
 as the cleanup can be performed using the tasks in the store and an associated external handler.
 
 ```php
 use Doctrine\DBAL\Connection;
 use Patchlevel\EventSourcing\Attribute\Cleanup;
 use Patchlevel\EventSourcing\Attribute\Projector;
-use Patchlevel\EventSourcing\Attribute\Setup;
 use Patchlevel\EventSourcing\Subscription\Cleanup\Dbal\DropIndexTask;
 
 #[Projector(self::TABLE)]
@@ -405,21 +401,18 @@ final class ProfileProjector
     private const TABLE = 'profile_v1';
 
     private Connection $connection;
-    
+
     #[Cleanup]
     public function drop(): array
     {
-        return [
-            new DropIndexTask(self::TABLE)
-        ];
+        return [new DropIndexTask(self::TABLE)];
     }
 }
 ```
-
 !!! note
 
     You can not mix the `cleanup` method with the `teardown` method.
-
+    
 #### Dbal Cleanup Tasks
 
 Default, we provide the following cleanup tasks for `doctrine/dbal`:
@@ -433,7 +426,7 @@ Default, we provide the following cleanup tasks for `doctrine/dbal`:
 
     You can create your own cleanup tasks and handler.
     For more information, see [Cleanup Handler](#cleanup-handler).
-
+    
 ### On Failed
 
 The subscription engine has a [retry strategy](#retry-strategy) to retry subscriptions that have an error.
@@ -1008,51 +1001,55 @@ $retryStrategyRepository = new RetryStrategyRepository([
 !!! tip
 
     You can change the default retry strategy by define the name in the constructor as second parameter.
-
+    
 ### Cleanup Handler
 
 You can also create your own cleanup tasks with associated handlers.
 First, create a task class that has all necessary information for the task.
 In our example, we create a task that deletes a collection from MongoDB.
 
 ```php
-final class DropCollection {
+final class DropCollection
+{
     public function __construct(
-        public readonly string $collectionName
-    ) {}
+        public readonly string $collectionName,
+    ) {
+    }
 }
 ```
-
 !!! warning
 
     The task class must be serializable. It will be stored in the subscription store.
-
-The next step is to create a handler for the task. 
+    
+The next step is to create a handler for the task.
 The handler must implement the `CleanupHandler` interface.
 
 ```php
 use MongoDb\Database;
 use Patchlevel\EventSourcing\Subscription\Cleanup\CleanupHandler;
 
-final class MongodbCleanupHandler implements CleanupHandler {
+final class MongodbCleanupHandler implements CleanupHandler
+{
     public function __construct(
-        private readonly Database $database
-    ) {}
-    
+        private readonly Database $database,
+    ) {
+    }
+
     public function __invoke(object $task): void
     {
-        if ($task instanceof DropCollection) {
-            $this->database->dropCollection($task->collectionName);
+        if (!($task instanceof DropCollection)) {
+            return;
         }
+
+        $this->database->dropCollection($task->collectionName);
     }
-    
+
     public function supports(object $task): bool
     {
         return $task instanceof DropCollection;
     }
 }
 ```
-
 Lastly, we have to add the new handler to `DefaultCleaner`,
 which is responsible for cleaning up subscriptions.
 
@@ -1064,11 +1061,10 @@ $cleaner = new DefaultCleaner([
     new MongodbCleanupHandler($mongodbDatabase),
 ]);
 ```
-
 !!! warning
 
     You need to pass the Cleaner to the Subscription Engine.
-
+    
 ### Subscriber Accessor
 
 The subscriber accessor repository is responsible for providing the subscribers to the subscription engine.
@@ -1088,7 +1084,6 @@ $subscriberAccessorRepository = new MetadataSubscriberAccessorRepository([
     $subscriber3,
 ]);
 ```
-
 ### Subscription Engine
 
 Now we can create the subscription engine and plug together the necessary services.
@@ -1098,13 +1093,13 @@ Finally, if we want to use the cleanup feature, we need to pass the cleanup hand
 
 ```php
 use Doctrine\DBAL\Connection;
+use Patchlevel\EventSourcing\Subscription\Cleanup\Dbal\DbalCleanupHandler;
+use Patchlevel\EventSourcing\Subscription\Cleanup\DefaultCleaner;
 use Patchlevel\EventSourcing\Subscription\Engine\DefaultSubscriptionEngine;
 use Patchlevel\EventSourcing\Subscription\Engine\MessageLoader;
 use Patchlevel\EventSourcing\Subscription\RetryStrategy\RetryStrategyRepository;
 use Patchlevel\EventSourcing\Subscription\Store\DoctrineSubscriptionStore;
 use Patchlevel\EventSourcing\Subscription\Subscriber\MetadataSubscriberAccessorRepository;
-use Patchlevel\EventSourcing\Subscription\Cleanup\Dbal\DbalCleanupHandler;
-use Patchlevel\EventSourcing\Subscription\Cleanup\DefaultCleaner;
 
 /**
  * @var MessageLoader $messageLoader
@@ -1120,9 +1115,7 @@ $subscriptionEngine = new DefaultSubscriptionEngine(
     $subscriberAccessorRepository,
     $retryStrategyRepository, // optional, if not set the default retry strategy is used
     $logger, // optional
-    new DefaultCleaner([
-        new DbalCleanupHandler($projectionConnection)
-    ]), // optional but required if you want to use the cleanup feature
+    new DefaultCleaner([new DbalCleanupHandler($projectionConnection)]), // optional but required if you want to use the cleanup feature
 );
 ```
 ### Catch up Subscription Engine