TaskPipeline is a container
I flirted with using League\Container in #12 (closed), which would replace the current TaskPipeline class. TaskPipeline is itself effectively a container, with the addition of getAllTasks(), which has no equivalent in PSR container classes. I left this for now, but want to revisit as its own issue. Should we:
- Extend League\Container to add a getAll() method (or per #75, make the extension an iterator),
- Use an alternate method to get a list of all available task IDs (for example, gather a list at discovery time to save outside of the container), or
- Rename the class as TaskContainer.
Edited by Mike Ryan