bytespin/console-command-scheduler-bundle
ConfigureBundleCommand using Symfony best practices: #[AsCommand] attribute, SymfonyStyle for user interaction, %kernel.project_dir% injection, --no-interaction support.PostInstallScript (dead code, raw I/O incompatible with Symfony Console).ext-readline dependency (no longer needed).ScheduledConsoleCommandEvent class extending Symfony\Contracts\EventDispatcher\Event with named constants (BEFORE, LOG, SUCCESS, FAILURE, AFTER).GenericEvent with ScheduledConsoleCommandEvent in handler and subscribers.SchedulerEasyAdminEventSubscriber from Doctrine\Common\EventSubscriber (removed in ORM 4) to #[AsDoctrineListener] attributes.#[AllowDynamicProperties] across the bundle, declare properties explicitly.Scheduler entity setters (DateTimeInterface|string|null).ConsoleJobsScheduler schedule loop.PostInstallScript checking for wrong bundle name (MessengerDedupeBundle).Configuration.php class declaration.SchedulerEasyAdminEventSubscriber (getExecutionuntilDate → getExecutionUntilDate).SchedulerLog::setReturnCode() to accept int|null (was string|null only).SchedulerLog::setDuration() to properly cast float to string.ExecuteConsoleCommand::$logFile default value from "" to null.ConsoleJobsScheduler.php-cs-fixer @Symfony code style across the bundle.README.md to include new mandatory configuration steps (manual or automatic) and checks.try/catch block for better management of potential exceptions during process execution.README.md to include instructions for manual bundle registration in bundles.php for users not utilizing Symfony Flex.How can I help you explore Laravel packages today?