Sequence and TemporalStateful should be the same interface
See original GitHub issueRight now, there are two abstract classes Sequence
for something with is an input sequence and TemporalStateful
which generates as a result of a computation. This in fact should be the same inerface, such that we can easily stack model parts.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Maintain Temporal Workflow Sequence - Community Support
Hi Team, I am totally new to temporal :slight_smile: I am building the food delivery workflow using temporal. A typical sequence of workflow ......
Read more >How are retries handled when activity interface has multiple ...
Hi, I have a use-case where one @ActivityInterface has multiple @ActivityMethod which are invoked in a sequence from the workflow.
Read more >Workflows in Java | Temporal Documentation
Workflow interface methods must have one of the following annotations: ... Workflows are stateful, so a new stub must be created for each...
Read more >Temporal Signal + Query Sequence Guarantee
our API logic is signal+query, can we assume that the temporal SDK/workers guarantee that when we guarantee the sequence of signal, ...
Read more >Workflows | Temporal Documentation
When those APIs are used, the results are stored as part of the Event History, which means that a re-executed Workflow Function will...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is done, but I can find the PR.
I created issue for the referencing (#576)