temporalio / temporalio/features
Provide extra/advanced details on start/execute workflow
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Describe the solution you'd like
Users may need ability to see some details about workflow start/execute beyond just the normal result they get. As of this writing, they may want to know it actually caused a workflow start (conflict policy doesn't always), its status to know whether it resulted in a workflow running (update with start sometimes operates on closed workflows), whether it was eagerly started, and the link on it if/when we're ready to expose links.
Requires some research, but early thoughts are that start options in different SDKs can have mutable placeholders where the start calls can set these details.
Per-SDK Tickets
- Go - TODO
- Java - TODO
- Core - N/A
- TypeScript - TODO
- Python - TODO
- .NET - TODO
- Ruby - TODO
- PHP - TODO
- 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
The issue identifies start/execute options across the Go, Java, TypeScript, Python, .NET, Ruby, and PHP SDKs as the scope; begin by researching how each SDK represents start options and workflow results. Define the extra details and per-SDK completion criteria, then track the SDK tickets until each listed implementation is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java, php, python, ruby, 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