-
Notifications
You must be signed in to change notification settings - Fork 148
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
Context Data Scoping #868
Comments
I think that to properly discuss this we need a pointer to the current section of the doc where $context and variable scoping is discussed. |
I opened dicussion #890. I think we need to discuss a few thing before considering this case. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
What would you like to be added:
Add a feature to enable scoping
$context
data.Why is this needed:
In some specific cases, a user might want to only provide a slice of its context data to sub tasks, which is especially true when performing iterations (for/while) to avoid useless bloating.
It is also true for parallel writes, which you'd rather have on a small slice of a potentially huge context than on its whole. Google Workflows addresses that by explicitly sharing variables.
The text was updated successfully, but these errors were encountered: