temporalio / temporalio/features
[Feature Request] Spec for expected client behavior when using handle or stub methods
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
https://github.com/temporalio/sdk-typescript/pull/468 changed the behavior of WorkflowHandle methods to use run_id only when a handle is created with one (getHandle in TS).
Handles created with start should follow runs by default and use first_execution_run_id for safety (don't operate on runs that aren't part of the same execution chain).
Handles created with signal_with_start should not use run_id but cannot yet guarantee safety, a server change is required for that.
getHandle should accept a first_execution_run_id for safety.
NOTE: signal, query and describe methods are unsafe at the time of this writing and require a server + API change.
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 with the behavior change described in temporalio/sdk-typescript#468 and the TypeScript getHandle entry point. Document expected behavior for handles created with start, signal_with_start, and getHandle, including run_id and first_execution_run_id safety; note the required server and API change for signal_with_start and the unsafe signal, query, and describe methods.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100