temporalio / temporalio/temporal
Add ability to reject signals by type
Nobody has claimed this yet.
- 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.
Sometimes a workflow needs the ability to reject signals that it is not listening to. For example a workflow that was canceled doesn't want to accept signals while it is performing cleanup.
Describe the solution you'd like
Add commands to enable/disable signal types. The signal type which is not enabled will be rejected synchronously.
BTW the same can apply to updates.
Describe alternatives you've considered
An update can be rejected, but it requires workers to run. This feature will generate rejection even if workers are down.
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 reviewing the existing signal handling and synchronous rejection behavior, then compare how updates are handled. The issue names no files, tests, or entry points. Done would mean unsupported signal types can be enabled or disabled and are rejected synchronously, including when workers are unavailable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100