index-node endpoint to get a hash from a block number
#3942
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
We're marking the GraphQL resolver for scalar values as async, like some other resolvers are already. This is needed to .await some calls in the new `index-node` endpoint.
|
Closes #3911. |
evaporei
approved these changes
Sep 16, 2022
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.
This new endpoint fills a need that several services (namely EBO and indexer agent) that rely on
graph-nodehave, i.e. to fetch a block hash starting from the number. The underlying implementation bridges over to the configured data ingestor for the requested network, allowing these services to get this data directly fromgraph-node.I've used some declarative macro idiosyncracy to quickly abstract over
BlockchainMapitems with different concrete types.