ChainedType vs SimpleTask #87
-
What is the advantage of using a chained task rather than a simple task list ? For example: // chained type
tasks:
chained:
type: 'chained'
single_run: true
description: 'chained tasks'
output: true
output_to_store: true
tasks:
command1:
type: 'command'
command: 'app:command1'
command2:
type: 'command'
command: 'app:command2'
command3:
type: 'command'
command: 'app:command3'
command4:
type: 'command'
command: 'app:command4' VS // simple FiFO tasks
tasks:
command1:
type: 'command'
command: 'app:command1'
single_run: true
command2:
type: 'command'
command: 'app:command2'
single_run: true
command3:
type: 'command'
command: 'app:command3'
single_run: true
command4:
type: 'command'
command: 'app:command4'
single_run: true This configuration has the advantage of giving information task by task, which is not found on a chained task. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
Don't get the point here, could you be more precise?
Actually, that's just a limitation on the display, not on the implementation, the goal that I have in mind is to display the informations of each embedded tasks when using the command: php bin/console scheduler:list
chained task
> sub-task
> sub-task |
Beta Was this translation helpful? Give feedback.
Don't get the point here, could you be more precise?
Actually, that's just a limitation on the display, not on the implementation, the goal that I have in mind is to display the informations of each embedded tasks when using the command: