Indexer support #146
Merged
Indexer support #146
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
abizjak
force-pushed
the
indexer-support
branch
2 times, most recently
from
90d485c
to
1ecf4d7
Compare
abizjak
force-pushed
the
indexer-support
branch
from
1ecf4d7
to
d0f126b
Compare
limemloh
approved these changes
Dec 8, 2023
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.
Purpose
We often need to traverse the chain to extract data from the transactions and events.
This has a bunch of boilerplate code, especially to do robustly.
This PR adds that scaffolding to the SDK so that in most circumstances the retrieval of data from the chain can be abstracted away, and retries are handled automatically.
The consumer can then focus on consuming the events only.
Checklist
hard-to-understand areas.