temporalio / temporalio/temporal
Use workflow raw history events API
Open
Nobody has claimed this yet.
difficulty: medium
enhancement
performance
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
Currently the workflow history events will be deserialized then serialized then deserialized again with passing to SDK
We should remove the unnecessary deserialized then serialized logic within frontend
Necessary changes need to be made in frontend and both SDKs
Contributor guide
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 tracing workflow history events through the frontend and both SDKs, focusing on where they are deserialized and serialized before reaching the SDK. The work is done when the raw history events API can pass events to both SDKs without the unnecessary frontend conversion cycle.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100