You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running a task with the process bundle, all "classic" output of Symfony are disabled to display a "log" trace which can not be read.
Those logs are useless. A computer can not read them neither an human can.
It will be great to have feedback like in a "normal" Symfony task, and it will be great if this output can be injected to the task to allow them making their own display.
var_dump or print_r should not be used to display data in the console. The normal Symfony output should be used, and each data display should have only one line, and should not be spread over two lines, like in all other Symfony commands.
The text was updated successfully, but these errors were encountered:
add information about removing the cleverage_process channel from the console output
add events on task resolution / loop iterations & find a way to allow to plug the Console OutputInterface into them (allowing custom output code without interfering with the process definition)
allow to plugin https://psysh.org/ without changing process definition ?
Description
When running a task with the process bundle, all "classic" output of Symfony are disabled to display a "log" trace which can not be read.
Those logs are useless. A computer can not read them neither an human can.
It will be great to have feedback like in a "normal" Symfony task, and it will be great if this output can be injected to the task to allow them making their own display.
var_dump
orprint_r
should not be used to display data in the console. The normal Symfony output should be used, and each data display should have only one line, and should not be spread over two lines, like in all other Symfony commands.The text was updated successfully, but these errors were encountered: