feat(deps): integrate resetter bundle

Author: Rastusik

composer.json

@@ -68,11 +68,11 @@
         "phpunit/php-code-coverage": "^10.1",
         "phpunit/phpcov": "^9.0",
         "phpunit/phpunit": "^10.5",
-        "pixelfederation/doctrine-resettable-em-bundle": "^7.0|^8.0",
         "ramsey/uuid": "^4.7",
         "rector/rector": "^2.0",
         "slevomat/coding-standard": "^8.14",
         "squizlabs/php_codesniffer": "^3.8",
+        "swoole-bundle/resetter-bundle": "^1.0",
         "swoole-bundle/z-engine": "^8.2.1|^8.3.0",
         "swoole/ide-helper": "^6.0.0",
         "symfony/debug-bundle": "^6.4|^7.2",
@@ -100,7 +100,7 @@
         "doctrine/orm": "For using Entity Manager Handler",
         "symfony/messenger": "For using Symfony Messenger Swoole Task Transport.",
         "upscale/swoole-blackfire": "To enable Blackfire profiling",
-        "pixelfederation/doctrine-resettable-em-bundle": "To be able to recover Doctrine Entity Managers from errors",
+        "swoole-bundle/resetter-bundle": "To be able to recover Doctrine Entity Managers from errors",
         "symfony/error-handler": "To use Symfony Error Handler",
         "swoole-bundle/z-engine": "To be able to use coroutines."
     },

composer.lock

@@ -313,7 +313,7 @@ them to the service pools for each resettable service. That means, there is no n
 Sometimes there are special cases that emerge for using Symfony with coroutines turned on, like pinging DBAL connections
 before the first query on each request (because the connections may be already closed, btw this bundle already has
 a solution for this, using connection pingers 
-from [pixelfederation/doctrine-resettable-em-bundle](https://github.com/pixelfederation/doctrine-resettable-em-bundle)).
+from [swoole-bundle/resetter-bundle](https://github.com/symfony-swoole/resetter-bundle)).
 
 For special cases like this, you can implement a custom service resetter. The resetter has to implement
 the `SwooleBundle\SwooleBundle\Bridge\Symfony\Container\Resetter` interface and has to be registered in the SF container

docs/configuration-reference.md

@@ -7,28 +7,28 @@ However this approach is quite simple and doesn't contain error handling logic f
 will get closed because of an error.
 
 For using Doctrine with this bundle in production, it is recommended to use the 
-[Doctrine resettable entity manager bundle](https://github.com/pixelfederation/doctrine-resettable-em-bundle).
+[Resetter bundle](https://github.com/symfony-swoole/resetter-bundle).
 
 This bundle will do the same as the handler mentioned above, but it does this for all the entity managers registered
 in the application. It automatically wraps all of them and instead only clearing the manager, it will also reset the 
 entity manager if it got closed during request processing. 
 
 ## How to use?
 
-You need to install the doctrine-resettable-em-bundle
+You need to install the resetter-bundle
 
 ```shell script
-composer require pixelfederation/doctrine-resettable-em-bundle
+composer require swoole-bundle/resetter-bundle
 ``` 
 
 After that, you need to activate the bundle in `bundles.php`.
 
 ```php
 return [
 // ...
-    PixelFederation\DoctrineResettableEmBundle\PixelFederationDoctrineResettableEmBundle::class => ['all' => true],
+    SwooleBundle\ResetterBundle\SwooleBundleResetterBundle::class => ['all' => true],
 // ...
 ];
 ```
 
-That's it! After that, all your entity managers will be able to handle all possibly occurring errors.
+That's it! After that, all your entity managers will be able to handle all possibly occurring errors.

docs/swoole-doctrine.md

@@ -5,7 +5,7 @@
 namespace SwooleBundle\SwooleBundle\Bridge\Doctrine\DBAL;
 
 use Doctrine\DBAL\Connection;
-use PixelFederation\DoctrineResettableEmBundle\DBAL\Connection\DBALAliveKeeper;
+use SwooleBundle\ResetterBundle\DBAL\Connection\DBALAliveKeeper;
 use SwooleBundle\SwooleBundle\Bridge\Symfony\Container\Resetter;
 use UnexpectedValueException;
 

src/Bridge/Doctrine/DBAL/ConnectionKeepAliveResetter.php

@@ -5,7 +5,7 @@
 namespace SwooleBundle\SwooleBundle\Bridge\Doctrine;
 
 use Assert\Assertion;
-use PixelFederation\DoctrineResettableEmBundle\DBAL\Connection\DBALPlatformAliveKeeper;
+use SwooleBundle\ResetterBundle\DBAL\Connection\DBALPlatformAliveKeeper;
 use SwooleBundle\SwooleBundle\Bridge\Doctrine\DBAL\ConnectionKeepAliveResetter;
 use SwooleBundle\SwooleBundle\Bridge\Doctrine\ORM\EntityManagerResetter;
 use SwooleBundle\SwooleBundle\Bridge\Symfony\Bundle\DependencyInjection\CompilerPass\StatefulServices\CompileProcessor;

src/Bridge/Doctrine/DoctrineProcessor.php

@@ -64,9 +64,6 @@
             "tests/bootstrap.php"
         ]
     },
-    "pixelfederation/doctrine-resettable-em-bundle": {
-        "version": "7.0.0"
-    },
     "squizlabs/php_codesniffer": {
         "version": "3.8",
         "recipe": {
@@ -79,6 +76,9 @@
             "phpcs.xml.dist"
         ]
     },
+    "swoole-bundle/resetter-bundle": {
+        "version": "1.0.0"
+    },
     "symfony/console": {
         "version": "5.4",
         "recipe": {

symfony.lock

@@ -8,7 +8,7 @@
 use Doctrine\Bundle\MigrationsBundle\DoctrineMigrationsBundle;
 use Exception;
 use Generator;
-use PixelFederation\DoctrineResettableEmBundle\PixelFederationDoctrineResettableEmBundle;
+use SwooleBundle\ResetterBundle\SwooleBundleResetterBundle;
 use SwooleBundle\SwooleBundle\Bridge\Symfony\Bundle\SwooleBundle;
 use SwooleBundle\SwooleBundle\Bridge\Symfony\Kernel\CoroutinesSupportingKernel;
 use SwooleBundle\SwooleBundle\Tests\Fixtures\Symfony\CoverageBundle\CoverageBundle;
@@ -101,7 +101,7 @@ public function registerBundles(): Generator
         yield new TestBundle();
         yield new DoctrineBundle();
         yield new DoctrineMigrationsBundle();
-        yield new PixelFederationDoctrineResettableEmBundle();
+        yield new SwooleBundleResetterBundle();
 
         if ($this->coverageEnabled) {
             yield new CoverageBundle();