Manage `files` & `globs` differently

The values are stored & retrieved perfectly with single tasks and serial chains.

But with large parallel chain, the known values aren’t 100% consistent. This is because ALL tasks & plugins are looking at & modifying the same internal variables: fly._.files, fly._.globs.

Ideas

Attach files and globs values to each fly.tasks entry.

• Will need a getter & setter for files() and globs(). These return & set the current task’s values.

• Will need a way to know what task is currently being executed.

[Akkuma]

So I read through some of the issue and one “farfetched” idea is to stop using this. It seems similar in nature to option 2. The idea would be for each task to be passed in the appropriate information and potentially return output to modify the input for the next plugin. Ultimately, this is just moving it to a functional style, so you just pass input and get output through the chain of plugins.

[lukeed]

@devmondo Thanks. I checked up on it and it looks like process.env goes way back, as I suspected / hoped.