Kevin Bond
Kevin Bond
Ability to add tasks to a "trigger group" like `deploy`: ```php class AppScheduleBuilder implements ScheduleBuilder { public function buildSchedule(Schedule $schedule): void { $schedule->addCommand('app:warm-cache') ->trigger('deploy') ->unscheduled() // disables task from bring...
- [x] Documentation
Throw exception if any tasks are scheduled at the same time. Should help with workaround (2) in #6.
See https://github.com/zenstruck/schedule-bundle/issues/39#issuecomment-790636785
- arguments: - `--limit=x` exit after running x tasks - `--memory-limit=x` exit after x memory reached - `--time-limit=x` exit after x tasks are run - add `schedule:stop-daemon` or `schedule:daemon --stop`...
I have found when multiple [`CommandTask`](https://github.com/kbond/schedule-bundle/blob/master/doc/define-tasks.md#commandtask)'s are due at the same time it can hit your PHP memory limit. I'm not sure what the best way to combat this is....
- `Task::getShortId(): string` - Display in `schedule:list` table (?) - Could make *force* running tasks from the CLI easier
Currently, all due tasks run synchronously in the same process. Utilizing Symfony Messenger would allow for adding due tasks to a queue to run asynchronously. I believe this could partially...
Wondering if it would be desired to add `LiveProp::$role`: ```php #[LiveProp(writable: true, role: 'OWNS_POST')] public Post $post; ``` When hydrating the property, we'd use `AuthorizationChecker::isGranted($liveProp->role, $post)` and throw an `AccessDeniedException`...