temporalio / temporalio/features
Explore ways of testing pre-patched code in SDKs
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
SDKs today only tests new workflow runs which means only the newer patch/getVersion code. Investigate (and implement) an approach to testing the pre-patched code. There are struggles with this such as the fact that some people patch with the expectation all pre-patched workflow runs are past a certain point. But it may be doable to assume a certain amount of commands/events are replaying thereby causing patch not to apply.
Per-SDK Tickets
- Go -
- Java -
- Core -
- TypeScript -
- Python -
- .NET -
- Ruby -
- PHP -
- 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 issue's distinction between pre-patched and newer patch/getVersion workflow runs, including the proposed replaying commands/events assumption. Use the per-SDK checklist to scope the work across Go, Java, Core, TypeScript, Python, .NET, Ruby, and PHP; done means pre-patched runs are covered, while Temporal CLI remains N/A.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, go, java, php, python, ruby, typescript
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100