-
Notifications
You must be signed in to change notification settings - Fork 135
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
*: Add support for local querying of Epoch and TAP subgraphs #1063
base: main
Are you sure you want to change the base?
Conversation
- For user, this change effectively adds support for local querying on epoch and tap subgraphs (previously only supported on network subgraph). - For contributors, this simplifies the codebase to have 1 SubgraphClient class instead of 3 separate implementations: EpochSubgraph, NetworkSubgraph and TapSubgraph.
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.
👍
e9f0894
to
9e514a9
Compare
Looks pretty good, I love the idea of having one more generalized class. |
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.
Great addition, we really needed this feature of indexing tap subgraph.
@carlosvdr still need to test on a running indexer! I won't merge this until I do so. |
Changes
EpochSubgraph
,NetworkSubgraph
, andTAPSubgraph
class implementations into a single, more generalized class:SubgraphClient
. By doing so support for local deployment querying is added for Epoch and TAP subgraphs.Background
The goal here is to add support for querying local deployments of the Epoch and TAP subgraphs. Instead of updating the EpochSubgraph and TAPSubgraph classes to that effect I merged those in with the NetworkSubgraph class which already has local querying support and auto switching between local and external based on health of endpoints.