temporalio / temporalio/features
[Feature Request] Add GetSignalInfo
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Is your feature request related to a problem? Please describe.
Some information about signals is not available within a signal handler. Example of this information is a time the signal was received by a workflow and signal eventId.
Describe the solution you'd like
Add GetSignalInfo call that can be called only from a signal handler and returns this information.
An option for Go would be adding GetSignalWithInfoChannel, which returns a Channel with Signal structures that include info + Value. This can be extended to return a single channel for all (or subset) of signals as this would allow guarantee in-order processing. Then the signal name would be a part of Signal structure.
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 existing signal-handler API in the Go SDK and review the requested GetSignalInfo behavior, including signal receipt time and eventId. Compare it with the proposed GetSignalWithInfoChannel design and its ordering implications; done means an agreed API that exposes the requested information only from a signal handler.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100