Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Passing a context object to the task functions #20

Closed
SamVerschueren opened this issue Jul 23, 2016 · 2 comments
Closed

Passing a context object to the task functions #20

SamVerschueren opened this issue Jul 23, 2016 · 2 comments

Comments

@SamVerschueren
Copy link
Owner

SamVerschueren commented Jul 23, 2016

In #17, the idea came up for passing a context object as argument of a task function. This would allow you to pass data from one task to another allowing you to create composable tasks.

Do we have to take something special into account when doing this? Because we are targetting Node 4+, are there any reasons why we should pass in a regular Object.create(null) object instead of Map?

@SamVerschueren SamVerschueren changed the title A context object Passing a context object to the task functions Jul 23, 2016
SamVerschueren added a commit that referenced this issue Jul 23, 2016
@otbe
Copy link

otbe commented Oct 17, 2016

Hi @SamVerschueren
any chances to see this merged soon? Would be awesome to use the output of a task in a successor task :)

Thanks for listr!

@SamVerschueren
Copy link
Owner Author

Will try to prioritize this. Thanks for the interest :).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants