- What does the piotrkreft/eager-resettable-services-bundle do?
- It is a Symfony bundle that eagerly resets resettable services so stateful dependencies start fresh between requests, long-running worker messages, and tests. The goal is to prevent stale in-memory state without requiring manual service resets. It focuses on Symfony's resettable-service lifecycle rather than Laravel's container or Octane workflows.
- Can I use piotrkreft/eager-resettable-services-bundle in a Laravel application?
- No, it is built as a Symfony bundle and is not a Laravel package. Laravel developers can review the approach when comparing state-reset strategies, but they should not expect it to integrate with Laravel's service container or HTTP kernel. For Laravel you would typically use framework-specific tooling or custom reset logic.
- How do I install piotrkreft/eager-resettable-services-bundle?
- Install it with Composer using composer require piotrkreft/eager-resettable-services-bundle. Then register the bundle in your Symfony application using the standard bundles.php or Kernel registration approach for your Symfony version. Check the repository README for exact setup details because the provided excerpt does not include configuration examples.
- When should I use eager resettable services in Symfony?
- Use it when your application has stateful services that must not carry data across requests, worker messages, or test cases. It is especially relevant for long-running processes where in-memory state can leak between jobs. The bundle handles eager resetting so you do not need to manually reset each service.
- Does this bundle help with Symfony Messenger workers and long-running processes?
- Yes, the overview explicitly mentions long-running worker messages as a target scenario. The bundle eagerly resets resettable services so each message can start with fresh dependencies. That reduces the risk of stale in-memory state accumulating during a worker's lifetime.
- Does piotrkreft/eager-resettable-services-bundle work in tests?
- The overview lists tests as one of the scenarios where stateful dependencies should start fresh. That makes it relevant when you need consistent service state between test cases. The exact test integration and configuration are not described in the provided excerpt, so review the repository for details.
- Do I need to mark my services as resettable to use this bundle?
- The bundle operates on Symfony resettable services, so your services need to participate in Symfony's reset mechanism. The provided context does not specify the exact tagging or interface requirements. Check the repository documentation for how to register or tag services for eager resetting.
- Which Symfony versions are supported by piotrkreft/eager-resettable-services-bundle?
- The provided context does not list supported Symfony versions. You should check the package's composer.json and repository release notes for the exact version constraints. That will tell you whether it fits your Symfony application's current version.
- How is this different from Symfony's built-in services resetter?
- Symfony already provides a services resetter mechanism for resettable services. This bundle focuses on eagerly resetting those services so stateful dependencies are refreshed between requests, worker messages, and tests. The distinction is the eager timing and intended scenarios rather than replacing Symfony's core reset contracts.
- Is piotrkreft/eager-resettable-services-bundle suitable for production?
- It is designed to address production concerns like stale in-memory state in long-running workers and repeated requests. However, the provided context does not include maintenance status, release history, or production usage reports. Evaluate the repository's activity, tests, and version constraints before adopting it in production.