temporalio / temporalio/features
Nexus serialization context
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
As an add on to #434 (and therefore after that), in addition to contextual workflow and activity info provided to converters/codecs, users need some Nexus info as well. Likely this is only "service" and "operation" due to our requirement of having the same contextual information on both sides of the serialization divide, but can be investigated.
Per-SDK Tickets
- Go -
- Java -
- Core - N/A
- 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
Start by reading issue #434 to understand the existing contextual workflow and activity information supplied to converters and codecs. Review the per-SDK checklist and investigate whether Nexus service and operation are the shared fields; done means the required Nexus context is available consistently across the supported SDKs.
Written by the indexing model from the issue text.
Assessment
- 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