nguyenngoclongdev
commented
2 days ago Thanks for your suggestions! But, as you know, there are two types of commands to run in the terminal:
- Commands that execute and end immediately
- Commands that execute and keep running So, relying on that to trigger a command for the next terminal might be a bit challenging.
What if we add an option called delay?
How about deciding when a terminal should execute based on this delay time?
When starting an array of tasks, multiple terminal windows are opened. Of course this is the way we want it. When doing so and running multiple commands (like starting dotnet core API's) the simultaneous execution of those services can take a lot of CPU and make the actions fail.
Describe the solution you'd like
It would be great to have functionality where I can set a dependency to another task. This can be done e.g. in docker where services are dependent on others and therefore can be executed after a previous one pas been executed