temporalio / temporalio/features
[Feature Request] Support dynamic workflows, activities, signals, queries, and updates in all SDKs
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
All SDKs should support "dynamic" workflows, activities, signals, and queries which are opt-in catch-alls when ones aren't registered for that worker (for workflows and activities) or workflow (for signals and queries).
- Go - https://github.com/temporalio/sdk-go/issues/543 and https://github.com/temporalio/sdk-go/issues/997 (not needed for signals, https://github.com/temporalio/sdk-go/pull/993 does this in a way)
- Java - Already done
- TypeScript - https://github.com/temporalio/sdk-typescript/issues/1015
- Python - https://github.com/temporalio/sdk-python/issues/242
- .NET - https://github.com/temporalio/sdk-dotnet/issues/27
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
Start by reviewing the linked Go, TypeScript, and Python issues and the referenced Go pull request; the Java SDK is already complete. Compare the behavior across the listed SDKs, then verify that each SDK supports opt-in dynamic workflows, activities, signals, queries, and updates where applicable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, go, java, python, typescript
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100