-
Notifications
You must be signed in to change notification settings - Fork 123
feat(sdk) : implement WorkflowHistory as a stream #1232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
emiling
wants to merge
8
commits into
temporalio:main
Choose a base branch
from
emiling:feature/issue-1213
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+104
−69
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
b6ea93f
temporalio/sdk-core#1213 add WorkflowHistoryStream for history event …
emiling 366f16c
temporalio/sdk-core#1213 add fetch_history_stream and helper for lazy…
emiling 121579c
temporalio/sdk-core#1213 implement streaming fetch for workflow execu…
emiling d048ad2
temporalio/sdk-core#1213 remove todo comment for stream implementation
emiling a7a857f
Merge branch 'master' into feature/issue-1213
emiling ac84eb6
temporalio/sdk-core#1213 make WorkflowHistory stream-based and retain…
emiling 4cc0255
Merge branch 'main' into feature/issue-1213
emiling a55e7ad
temporalio/sdk-core#1213 make WorkflowHistory stream-based and retain…
emiling File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think rather than having two totally separate APIs, we can just change
WorkflowHistoryto become like your new stream-based type. Since we're still in pre-release we can change the public API.We can keep
into_eventsas a helper for people who would rather consume it all at once.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Sushisource Originally, I separated this out to maintain backward compatibility. Since we're still in pre-release and public api changes are fine, I’ve updated it to use the stream-based WorkflowHistory as suggested. Thanks for the suggestion!