Fix types for stream calls #1040
Open
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
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.
I was attempting to listen to a transaction or operation stream on Horizon and I noticed that the types are sent back completely wrong.
i.e. I would try to call
.records,.next()or.previous()operations and it would obviously fail as streams do not give collectionPages but rather single operationRecords. Same happens with transaction streams, etc.here is after the fix with the correct types:
So I then went in and fixed the line so the types are correct since it's a very tiny fix.
TLDR: in typescript, streams were typed as Collections/pages when in reality they were single records.