temporalio / temporalio/features
Concept of "workflow local" value
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Describe the solution you'd like
Users need a thread-local-like way to access/mutate workflow-specific values. This already exists in Java.
Per-SDK Tickets
- Go - https://github.com/temporalio/sdk-go/issues/1760
- Java - Already exists
- Core - N/A
- TypeScript - N/A: thanks to the Sandbox, globals are already "workflow local"
- Python - https://github.com/temporalio/sdk-python/issues/719
- .NET - https://github.com/temporalio/sdk-dotnet/issues/387
- Ruby - https://github.com/temporalio/sdk-ruby/issues/179
- PHP - https://github.com/temporalio/sdk-php/issues/545
- Temporal CLI - N/A
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the existing Java behavior and the linked Go, Python, .NET, Ruby, and PHP tickets first; this issue names no repository files or tests. Define the workflow-local API and behavior for each applicable SDK, with completion reflected by resolving the relevant per-SDK tickets consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, go, java, php, python, ruby, typescript
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100