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
(Side Note, sorry for all the issues I'm submitting...I"m in the middle of refactoring a large number of Toastfiles so it's on my mind 😄 I'm also a big fan of Toast!)
Description
Add the ability to print out the task schedule in order.
Alternatives considered
None
Additional context
While doing some larger refactoring of my toastfiles I found myself working through the dependencies of my tasks to make sure the order of execution came out right, and thus shared layers between the various components. The only way I could do this was to run trough the toastfile though by actually running the tasks.
Adding a simple --print-schedule would solve this and allow one to work through the order and ensure dependencies are correct before running the tasks.
I have a working implementation of this read for a PR if interested.
The text was updated successfully, but these errors were encountered:
I can see how this would be useful for you, though I have similar thoughts as in #389 (comment). These "inessential" features are starting to pile up, and Toast is already getting too complicated in my opinion. So each new feature needs to be sufficiently justified. I don't have a good sense of how broadly useful this would be to Toast users in general.
For now, I will leave this issue open for further discussion.
(Side Note, sorry for all the issues I'm submitting...I"m in the middle of refactoring a large number of Toastfiles so it's on my mind 😄 I'm also a big fan of Toast!)
Description
Add the ability to print out the task schedule in order.
Alternatives considered
None
Additional context
While doing some larger refactoring of my toastfiles I found myself working through the dependencies of my tasks to make sure the order of execution came out right, and thus shared layers between the various components. The only way I could do this was to run trough the toastfile though by actually running the tasks.
Adding a simple
--print-schedule
would solve this and allow one to work through the order and ensure dependencies are correct before running the tasks.I have a working implementation of this read for a PR if interested.
The text was updated successfully, but these errors were encountered: