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
In case of output: prefixed, if we have a task calling an internal task (see ex taskfile above), prefix used for internal task should be caller task's prefix to completely hide internal task.
I have put two levels of calling in this exemple to explicitly see that prefix should be inherited from direct caller only.
If prefix is customized on caller, then internal callee should use this one.
If prefix is customized on internal task, then there shouldn't have inheritance.
The text was updated successfully, but these errors were encountered:
We have Taskfile's which represent fairly complex workflows, most of the Tasks themselves are internal, and we have a fair amount of inheritance, and also deps (and everywhere else a Task might reside). If all of our internal tasks would have the same prefix as the "external" ones then it becomes very difficult to understand what is happening as a task/workflow executes, and consequently, difficult to debug.
In case of
output: prefixed
, if we have a task calling an internal task (see ex taskfile above), prefix used for internal task should be caller task's prefix to completely hide internal task.taskfile.yml :
actual output of :
task external
expected output :
I have put two levels of calling in this exemple to explicitly see that prefix should be inherited from direct caller only.
If prefix is customized on caller, then internal callee should use this one.
If prefix is customized on internal task, then there shouldn't have inheritance.
The text was updated successfully, but these errors were encountered: