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

Context Data Scoping #868

Open
cdavernas opened this issue May 30, 2024 · 6 comments
Open

Context Data Scoping #868

cdavernas opened this issue May 30, 2024 · 6 comments
Labels
area: spec Changes in the Specification backlog The issue has been recognized but not yet scheduled or prioritized change: documentation Improvements or additions to documentation. It won't impact a version change. change: feature New feature or request. Impacts in a minor version change
Milestone

Comments

@cdavernas
Copy link
Member

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.

@cdavernas cdavernas added change: documentation Improvements or additions to documentation. It won't impact a version change. change: feature New feature or request. Impacts in a minor version change area: spec Changes in the Specification labels May 30, 2024
@cdavernas cdavernas added this to the v1.0.0-alpha2 milestone May 30, 2024
@fjtirado
Copy link
Collaborator

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.

@fjtirado
Copy link
Collaborator

fjtirado commented Jun 6, 2024

I opened dicussion #890. I think we need to discuss a few thing before considering this case.

Copy link

github-actions bot commented Aug 4, 2024

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.

@cdavernas cdavernas self-assigned this Aug 21, 2024
Copy link

github-actions bot commented Oct 6, 2024

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.

Copy link

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.

Copy link

github-actions bot commented Jan 7, 2025

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.

@cdavernas cdavernas modified the milestones: v1.0.0, v1.1.0 Jan 10, 2025
@cdavernas cdavernas added the backlog The issue has been recognized but not yet scheduled or prioritized label Jan 10, 2025
@cdavernas cdavernas removed their assignment Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: spec Changes in the Specification backlog The issue has been recognized but not yet scheduled or prioritized change: documentation Improvements or additions to documentation. It won't impact a version change. change: feature New feature or request. Impacts in a minor version change
Projects
Status: Backlog
Development

No branches or pull requests

2 participants