feat: process queued items concurrently #17
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Queued items are now processed concurrently, and state changes are emitted more often. BREAKING CHANGE: If a user provides one of the activity functions (for workflows, tasks or work items), state change will be emitted immediatelly after user "advances" the state (manually calls `startTask`, `completeWorkItem` or one of the similar functions. Whatever was enqueued during the current "turn" will be processed concurrently. For instance if you initialize and enqueue start of multiple work items, they will be started concurrently. Previously, they were processed sequentially.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Queued items are now processed concurrently, and state changes are emitted more often.
BREAKING CHANGE: If a user provides one of the activity functions (for workflows, tasks or work items), state change will be emitted immediatelly after user "advances" the state (manually calls
startTask,completeWorkItemor one of the similar functions.Whatever was enqueued during the current "turn" will be processed concurrently. For instance if you initialize and enqueue start of multiple work items, they will be started concurrently. Previously, they were processed sequentially.