temporalio / temporalio/features
[Feature Request] Consider higher-level activity options for some languages
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Is your feature request related to a problem? Please describe.
TypeScript and Java both support setting activity options at the workflow level for all activities of a type. Java even supports setting default activity options for all activities. Go and Python support neither of these.
Outstanding questions:
- Should we support workflow-activity-type-level options in Python or is it expressive enough that they can pass options around?
- Should we support workflow-activity-type-level options in Go, or is there concern about how it would merge given zero-types of some values?
- Should we support workflow-level default activity options for TypeScript, Python, and Go?
This intentionally doesn't discuss contextual activity options like only Go has or invocation time options like only Python has
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 comparing the existing workflow-level and activity-type-level options in the TypeScript and Java SDKs with the capabilities described for Go and Python. Define the desired behavior and option-merging rules for workflow-activity-type-level and workflow-level defaults, with the outstanding questions resolved for each SDK.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java, python, typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100