temporalio / temporalio/features
[Feature Request] Block when workflow commands are produced in a read only context
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.
Block users, in some language appropriate way, from producing workflow commands in a read only context . Currently read only contexts are query handlers and update validators
Describe the solution you'd like
In Go I would expect the workflow task processing to panic. In java probably throw an exception. In either case I would epxet the workflow task to fail, but not the whole workflow.
- Go - https://github.com/temporalio/sdk-go/issues/1000
- Java - https://github.com/temporalio/sdk-java/issues/1748
- Core?
- Typescript
- Python
- Dotnet
- Ruby ?
- PHP ?
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
Read the linked Go and Java issues first, then compare how query handlers and update validators produce workflow commands in the relevant SDKs. Define the behavior for each unchecked SDK and verify that an invalid workflow task fails without failing the whole workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100